Thanks for the info Roger and everyone else. >From what I could tell, trapping appStopEvent is the easiest way to keep the user in the app, and it doesn't look like it would cause any problems. I was trapping keyDownEvent for the hard keys, application soft key, etc., but that doesn't work in edge cases, like where the user hits an application button while they have the soft keyboard open . . . the app will quit. Trapping appStopEvent, along with capturing program status state as suggested below, simplifies the application logic and seems to be the "best" solution for this scenario. (Also, trapping all sorts of keyDownEvents makes the AppEventLoop slower and more complicated :)
Cheers, -DGA > > Actually not that unusual a request. > > By all means trap appStopEvent. It'll catch 95% of the problem. > But its not really necessary > > You'll also need to keep track of the program status for when the > user does a RESET or your program fails, and then put some code > in the sync software to not sync a database with incomplete data. > That should catch the other 5% (or if you don't bother with trapping > appStopEvent it'd trap all 100%) > > Roger Stringer > Marietta Systems > > > -- > For information on using the Palm Developer Forums, or to > unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
