According to Palm OS Companion, page 57
#############################################################################
Global variables are generally only allocated after an application receives
sysAppLaunchCmdNormalLaunch (see Listing 3.2) or sysAppLaunchCmdGoto; so if
the application hasn't received either of these launch codes, its global
variables are usually not allocated and not accessible.
#############################################################################
However, I introduced a custom launch code
typedef enum {
myAppCmdGoToListView = sysAppLaunchCmdCustomBase
} MyAppCustomActionCodes;
When testing myAppCmdGoToListView with a
SysUIAppSwitch (cardNo, dbID, myAppCmdGoToListView, NULL);
job, I see that the global vartiables ARE allocated and ARE accessible.
Is this deliberate and can I count on it in the future too or this is just an
undocumented feature?
I used OS 3.3
Please advise me ASAP! Thanks.
Best regards, Paul [pedit: http://www.math.ohio-state.edu/~nevai/palm/ ]
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
