Thanks for the notes John. > Note for example that the Palm OS Reference specifically > forbids ignoring > appStopEvent (Event Reference, p71). While the documentation > shouldn't > be taken as infallible, IMHO it's safer to think more carefully about > what you really want to ban, and instead consume keyDownEvents for the > launcher and application buttons before you pass them to > SysHandleEvent. >
I agree about trapping specific keyDownEvents, but unfortunately that doesn't work well in cases where the user pops up the soft keyboard on a form, and then hits a hard key. Since the keyboard has its own event loop, it will allow the app to exit, when I don't want it to. I'm a little confused as to your doc reference: I looked at p. 71 as you suggested, and didn't see anything that specifically forbids ignorning appStopEvent. On p. 71 I saw the following: "appStopEvent When the system wants to launch a different application than the one currently running, the event manager sends this event to request the current application to terminate. In response, an application has to exit its event loop, close any open files and forms, and exit. If an application doesn't respond to this event by exiting, the system can't start the other application." I'm using the OS 4 SDK version of the docs. Is there other, more current documentation available? The way I read this, an app "should" exit the event loop, close files and forms and exit, and if it doesn't the other app won't start. I take this to mean that if appStopEvent is ignored, then other apps won't get started (which is what I need :) Cheers, -DGA -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
