The "How do I bail out in case of an error" is an important question. I'd like to have try/catch constructs, for my Palm applications. What are the requirements for such a mechanism? i.e. What components of the operating system could have been compromised by a rogue application, how do I check them, and how do I fix them? Probably, PalmOS already has this kind of cleaning up... Bob Ebert wrote: > At 2:08 AM +0100 27-01-00, Scott Johnson (WA) wrote: > >It's Palm VII Clipper. The Back (arrow) button at the top of the screen > >takes you all the way "back" to the launcher. Heh heh. :-) > > But that makes sense, since the launcher is also the master list of PQAs. :-) > > Anyway, if you want to 'exit' an app by launching the launcher, that's > pretty easy, just call UIAppSwitch and specify the launcher. > > Of course, you still have to run your own event loop until you get the > appStopEvent, so it's no help for the original poster's question which was > 'how do I bail out in the case of an error?' > > How the built-in apps bail out in the case of an error is with > ErrFatalDisplay or ErrFatalDisplayIf. These offer the only 'true' error > recovery, which is to reset the device. Just exiting your app won't help > if you've made a truly bad error, because you'll probably have trashed the > heap so the next app to run will crash instead. ...so you may as well just > tell the user and let them reset. > > --Bob > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see >http://www.palm.com/devzone/mailinglists.html -- Sergio Carvalho --------------- [EMAIL PROTECTED] [EMAIL PROTECTED] If at first you don't succeed, skydiving is not for you -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palm.com/devzone/mailinglists.html
