Sigh... A search through the archives for "sysAppLaunchCmdDisplayAlarm" yielded in only 70 messages. I read them all. Only one of them is really relevant to my problem - this one:
http://news.palmos.com/read/messages?id=31795 It's from somebody who is experiencing exactly the same problem. And - surprise, surprise - nobody answered his plea for help, either. :-( I seem to have a knack for enountering problems for which people don't know the solution... :-(( Apparenly, for some unknown reason, you can't have a normal event loop from an alarm, either - not just from a volume mounted notification. It's just that you can display a bit more (i.e., you don't terminate immediatelt) when doing it from an alarm. However, the fact that things work almost perfectly when there *is* a start.prc to launch gave me an idea - why not just always launch myself (with a custom launch code) from the alarm? (This didn't work from the volume mounted notification.) Well, this apparently works - or at least I haven't found yet the case that breaks it... So, when the volume mounted notification arrives, set an alarm. When the alarm triggers, launch yourself. When launched with a custom code - finally! - scan the memory card. Flying from New York to London through Honolulu... Arrgggh, systems programming for this OS really sucks. :-( Now, my application doesn't use any global or static variables - honest. But all these failures to go through its normal forms and run an event loop from notifications and special launch codes (and success when launched normall or with a custom launch code) look as if *something* is trying to access unavailable global variables... I wonder - does using the normal user interface (you know, the Frm* functions) somehow use internal global variables or something - and that's why it causes problems when used from notifications and special launch codes? Regards, Vesselin -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
