The FAQ in the Knowledge Base ("How does SysUIAppSwitch work?") is telling me
that SysUIAppSwitch will switch back. I'm attaching that below. Anyway,
that's definitely what I'm seeing so far, although I hope a common sense answer
like yours will prevail here!
App B is proven to quit normally, so it's not invoking another switch. App A
is correctly switching to App B on its first attempt at SysUIAppSwitch. I
haven't got any reason to think App A is calling SysUIAppSwitch again before it
quits, for example...
Is the experience of many that SysUIAppSwitch starts B and ends A properly?
That might point to some kind of version issue. I've tested on the Palm OS 3.5
emulator and a device.
Thanks again.
Shane D.
-----------------------------------------------------------------
>From the Knowledge Base:
Internally, SysUIAppSwitch works like this:
1. Set OS setting for "next application to launch" to passed app
2. Post an appStopEvent to the current application
When you application ends due to receiving the appStopEvent, the OS does this:
1. Save "next app to launch" in a local variable
2. Set "next app to launch" to the application that just ended
3. Launch the new application
So, if you're in A and SysUIAppSwitch to B, then when B ends the OS will
relaunch A unless something's disturbed that "next app to launch" value, such
as the user hitting a hard button or B calling SysUIAppSwitch.
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
