My thought: If your app is that fragile, just keep getting the time in
seconds.  When there is a big difference between the last time stamp saved
and the current time stamp you can check to see if you need to reset your
process/app.  If you are continually watching the clock, it should not vary
more than a few seconds between checks while your app is running.  This
should also allow you to gracefully handle beaming and low battery warning
interruptions without compromising the Palm.



-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Reply via email to