<i><font color="#663300"><i><font color="#663300">This question is mainly directed to Ed but if you know what's going on, please don't hestitate to answer!
I just downloaded Codebook 6.1 and started a new project with it. It would seem that there have been some changes made to the menu class structure. ( I didn't choose the .mpr installation option )
I was wondering if the procedure to add menu pads, bars, popups, etc. still involves using the loadchildren() method? I didn't see any code there so I'm assuming there are some marvelous new additions/revisions to it that I can take advantage of? This line of thinking was brought on by a thread authored by Ed ( message#6204 ), otherwise I would not have been able to get the thing to run without a glitch.</font></i>
The original ChildCollection classes required hard-coding the process of loading the child class information into the array property. In Codebook 6.1, menus are subclasses of the <b>cChildListCollection</b> class, which uses a property called 'cChildList' to hold the child object class names in a comma-separated list. To add, remove or reorder a menu, just change this property.
One limitation of this method is that properties are limited to 254 characters, and some menu popups required more. As a shortcut, I've added a keyword '<b>sep</b>' to the cPopup class as a shorthand for the separatorbar class. When it sees 'sep', it substitutes whatever class is specified in the <b>cSeparatorBarClass</b> property.
</font></i>
Thanks Ed,
I always hated having to hard-code the child loading process, and rarely ever got it to work the first time around. Your method makes it a hell of alot easier and more efficient in my books!
Regards,
Richard Canning
Atlantic DataSystems Inc.
St. Johns, NF, Canada
©2001 Richard E Canning |
