Greetings all, I've got an unusual requirement for an application which requires strict data validation on Palm devices. As such, all records must be validated before they are saved, and the customer doesn't want to lose any data that may have been entered. So the application cannot allow users to leave the app while editing a record, as the record could be left in an invalid state, and then synced to a server where it would create havoc among back office systems, etc.
The customer would like the application to not allow users to leave the application while editing records, period. It appears the easiest way to do this is by conditionally handling appStopEvent in the AppEventLoop: if appStopEvent is seen, and the user is editing a record, set the event to a nilEvent and popup a notification dialog. I looked back through the archives and found a few similar discussions about ignoring appStopEvent and none mention impacts other than "your app won't exit", but I'm a little concerned that there may be some memory leaking somewhere if I don't allow appStopEvent. I'm specifically concerned about things like beam receiving, where data is received and then the app is switched to a display app (ie: the launcher in the case of receiving a beamed app). I made a little test app to check this (it traps appStopEvent unless a specific button is pressed), and it doesn't seem to be causing any problems with receiveing beamed apps, but I wanted to get other opinions as to what other impacts there may be on stability or overall app robustness by trapping appStopEvent. Thoughts? Comments? ( Threats? :) -DGA -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
