> When I receive control with the custom launch code from
> SysAppLaunch, do I have to eat events until the first
> appStopEvent and only *then* enter my normal event loop??
OK, the exit event apparently comes from the Launcher? I tried eating it. This works *if* it is the Launcher running when the volume mounting notification arrives. If it is some other application, I never get the exit event and the whole thing hangs.
If I *don't* eat the exit event, everything works *if* some application other than the Launcher is running when the notification arrives. It doesn't have to be my application - it could be the Calculator or anything else. But if it is the Launcher that is running, I crash.
I don't understand why this is happening. :-( But one way to solve it would be to determine whether it is the Launcher that is running when the notification arrives.
How do I do that? And what about third-party launchers?