Since he already has the 99 identifiers, he could continue to use them, he doesn't have to use the ID generation that RE provides. Just so long as he is careful to name his new resources the same pattern that constructor uses. The C header mechanism that RE uses may need to be reworked to match Constructor. Ben has made me aware of that (painfully aware).
As for show/hide form objects, that feature is planned for the next version. It will be a toggle that shows/hides form objects based on the "usable" quantity. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Luc Le Blanc > Sent: Friday, January 14, 2005 10:16 PM > To: Palm Developer Forum > Subject: Re: Constructor's 99 resource limit > > But if he already has 99 objects in a single form, he likely > has support code to interact with the form, so the ability to > have the Palm OS Resource Editor generate a header file with > Constructor's ID scheme would let him use his code unmodified > instead of editing all referenced object IDs. There is still > a slight bug with the ID generation grammar in the Editor > that prevents this. I'm in the same situation, but with a > dozen forms (with a few tabbed dialogs reaching the 100 limit). > > Of course, the ability to hide disabled objects in the Palm > OS Resource Editor (as does Constructor) would be almost as > important to edit context-adaptive forms. > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
