Subject Re: Custom components name parameter From Russ Fisher <rfisher@ccnintl.com> Date Fri, 13 Dec 2019 13:29:20 -0500 Newsgroups dbase.getting-started Ken Mayer Wrote: > On 12/13/2019 9:02 AM, Russ Fisher wrote: > > At the end of Phase IV of the tutorial where you have just created all the custom components, you are advised to edit the Mycontrols.cc file and remove the "name" parameter from all the class definitions.  In his book, Ken Mayer goes into more detail about the reason for this, stating that dBase streams out the wrong name for the class. > > > > My question is, is there ever a time when you would WANT that behavior?  If not, then why, after so many generations of dBase, have the devs not fixed that - to either stream the correct name or remove the parameter from any class definitions based on a custom class?  That would eliminate one more "thing" you have to remember to change while designing or editing an application. > > > > I don't know of a time, the problem is the name that gets streamed out > is seldom what you want to use. As to the developers fixing it, it's a > simple enough thing for you to do when building your custom library. I > think if it is in the bug database it's probably a pretty low priority. > > Ken > Hi Ken, I don't dispute that it's an easy thing to do.  It's just one more thing you have to "remember" to do.  Even if you make a minor change to a custom control's definition and re-save it, you have to remember to clear the parameter. As a side note, while creating custom controls, the first 8 or 9 appeared in the custom control palette immediately upon my saving them.  After that, I started noticing that they weren't there and would only appear after closing the IDE down and restarting it.  Why??? Not to be disparaging, because I still think this is a fantastic product, but it just seems that before a software company releases a totally new version, any and all outstanding "bugs" from the previous one(s) should be cleaned up in the new release, ESPECIALLY since they charge you 80% of the cost of a full release to "upgrade".  I understand that there will always be bugs in any software, but if they are KNOWN, they should be fixed BEFORE any new features are added. Thank goodness for this community and especially people like you with your outstanding tutorial and books.  A person relying solely on the documentation that comes with the product would be totally lost and confused. I'll climb off my soapbox now - sorry for the rant. Cheers, Russ