This has been discussed in some detail before but I'd like to emphasize that IMO dynamic control creation is completely broken in PalmOS 3.0. There should be big big warnings in the manuals and in the knowledgebase about this. Anybody having access to the 3.0 sources and wanting to create controls on the fly should have a closer look at PrvFixupPointers() in form.c. Roger must have had a very bad day when he wrote this. I wonder how a code like this ever slipped through code review. In essence, you should NEVER use any of the dynamic control creation functions FrmAddSpaceForObject, FrmRemoveObject, FrmNewLabel, FrmNewBitmap, CtlNewControl etc. on PalmOS 3.0 or your bound for all kinds of trouble. In my case, a popup trigger stopped working after I dynamically added a control because PrvFixupPointers apparently changed something in its control structure. This only happened when the app was loaded to certain memory locations. It was never detected in Gremlin runs.... Devsupp, as usually, is only auto-responding so here's my question: Has this been fixed in a subsequent release of PalmOS? Will there be a OS update (not the 3.3 flash) for PalmOS 3.0 (and PalmOS 3.2)? Regards, Andreas http://linkesoft.com PS: POSE is such a great tool, but running 1 million gremlins does not even come close to having a few thousand humans run the application on a real device :-) PPS: This forum is unbeatable. I would have never looked into this by myself. Thanks to Palm for hosting such a great mailing list. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palm.com/devzone/mailinglists.html
