> 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.
It makes sense that globals would be allocated here -- you are explicitly
launching a new program through the SysUIAppSwitch call. The main reason
why the system would not allocate globals for an application would be
because another program is running and should continue to run after your
program deals with the launch situation. See "SysAppLaunch" which calls
another program as a subroutine of yours for a situation like that.
> Is this deliberate and can I count on it in the future too or this is just
an
> undocumented feature?
I don't see explicit documentation, but I think your expectations are very
reasonable and would hope that Palm documents the behavior as such.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
