Besides, I still don't understand why the program I posted above crashes if the notification arrives when the Launcher is running. OK, so for some bizarre reason the Launcher posts an appStopEvent (you know, the kind of thing all newbies are told *not* to do when trying to exit an application). So, my application's event loop terminates immediately. Fine, I would have understood if, as a result, my application did nothing. But why the crash?! And the crash happens *after* my application quits - it seems as if it is the Launcher itself that's crashing...
Actually, Launcher doesn't directly post an appStopEvent. It just calls SysUIAppSwitch to relaunch itself with a custom launch code to tell it to refresh everything and show the launcher page for the just-inserted volume. SysUIAppSwitch posts the appStopEvent. When you call SysUIAppSwitch, a second appStopEvent is put in the queue, but there's only one system global to tell the OS what to launch next, so the launcher ends, your app starts, and it immediately has an appStopEvent to deal with.
-- Ben Combee, Senior Software Engineer, palmOne, Inc. "Combee on Palm OS" weblog: http://palmos.combee.net/ Developer Forum Archives: http://news.palmos.com/read/all_forums/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
