I stop writing Palm apps for six months and everything changes :-) I'm trying to debug a popup trigger problem and went to do what I'd normally have done last year - look at what the control properties are being set to. After managing to recompile my project so that I could examine the form data without counting bytes in the hex editor (note to "Targeting the PalmOS platform" maintainer - the Debugging section could do with a short discussion of how to do this. It would also help if the ALLOW_..._FORMS #define switched on ALLOW_..._WINDOWS so that the FormType didn't raise an error during compilation) I've run into a problem.
While stepping through the code the other properties of the form look fine but numObjects is zero and the objects array pointer is undefined. This situation remains even while the form is visible on the screen. This is under the Release PalmSim (the debug PalmSim doesn't produce the problem I'm trying to trace). Under the debug PalmSim the form pointer isn't even valid - it's pointing to freed memory (FEFEF, or is that unallocated?). Any guesses as to what I'm doing wrong? Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
