In other words, when you launch your app 'normally', it received the
'sysAppLaunchCmdNormalLaunch' launch code, and it has access to ALL of
its global data (variables, etc.), and all code in all segments. When
the app launches from another launch code (responding to an alarm,
reset, synch, etc.), neither the globals or other segments are
available. Trying to access those things when they don't exits will
usually cause a crash. So, if you plan to respond to the non-normal
launch codes, you have to ensure that all your functions pass the
required data to each other, or that each function can find the data by
reading it from a database, prefs, feature etc. Bob.
Mikhail Barashkov wrote:
In particular, all functions in your application called while
processing a launch code that doesn't give you globals must be in the
main code section. This always includes PilotMain, which is always
called by the startup code for all launch codes.
------------------------
I have no idea what this is trying to tell me. What does it mean
"must not attempt to call between different sections when globals are
not available"?
It means you have to use only your main segment when launching your
app without access to globals (e.g., app launch by the "Search" silk
button).
Regards
Mikhail Barashkov
http://www.handydev.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
