> Seems you have a lot of hazzle with this... You bet I do. :-( Well, it works now that my application is launching itself with a custom launch code when the alarm arrives - but I still would like to know why my previous code didn't work.
> so try this version, which I had before I switched to FrmDoDialog Thanks. I'm trying to figure out in what way it differs from my original code... I do the things in a slightly different order - FrmInitForm/FrmSetActiveForm/FrmSetEventHandler/FrmDrawForm as opposed to your FrmInitForm/FrmDrawForm/FrmSetActiveForm/FrmSetEventHandler - but that probably doesn't matter. One important difference is that you do oldForm = FrmGetActiveForm(); at the beginning and FrmSetActiveForm(oldForm); at the end - perhaps this is the way to avoid the blank screen when my application exits? When an alarm triggers and your application (that is servicing the alarm) hasn't shown any user interface yet, does FrmGetActiveForm return the active form of the application that was interrupted by the alarm (e.g., possibly that of the Launcher)? Regards, Vesselin -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
