I'm writing an app using Palm Object Library (POL) and have several objects that define global variables. Their methods are only used when the app gets a normal launch, but of course the constructor is called every launch resulting in Debug errors notifying me that uninitialized globals are being used every time I stop the emulator (sysAppLaunchCmdReset). At this point the only launch code I'm using is normal launch but I will eventually be using alarms though once again that code will not depend on any global variables.
1.) Do I have to worry about this in a finished product? Can I just ignore it or does it have an adverse impact on other applications?
The constructors for global variables should only be called for launches that support global variables. This is how things are coded in the Palm OS Runtime library used by CW.
Are you sure its not a different problem? You can use the CW debugger to simulate starting your app with a different launch code and use that to see how the POL code handles it. I've got a fairly major POL app with several global classes that handles both global and no-global launch codes without problems.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
