on 12/3/2001 7:24 AM, John Marshall at [EMAIL PROTECTED] wrote: > On Mon, Dec 03, 2001 at 09:52:34AM -0500, Avilla, Dane wrote: >> 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. > > Yes. Many bets are off when things with their own event loops have > popped up. This caused David Kendall's problem, and lots of other > problems people encounter regularly too. > > IMHO your only good answer is "don't do that". Don't let the keyboard > dialog or anything else with its own even loop come up when you need > to prevent your app from quitting. But I suspect your users won't > like that... >
I'm not sure that forbidding the user from exiting is a great UI, but from a technical point of view, there's no problem in just ignoring appStopEvents. Feel free to let other stuff with event loops come up. Having anything else with an event loop doesn't affect whether your application quits or not. Eventually, the inner event loop exits, returning control to your application. At that point, there's an appStopEvent in the event queue, which you can ignore. Neil -- Neil Rhodes [EMAIL PROTECTED] Available for contract programming Coauthor: Palm OS Programming: the Developer's Guide, 2nd edition (O'Reilly) -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
