> State the nature of the terminal error and call ErrFatalDisplay (which puts
> up that dialog with the reset button) Its not very graceful but it seems
> to be accepted practice for most Palm apps.
maybe in the first days - but surely, "reset" = bad for user.
i moved away from the ErrFatalDisplay... routines to give the
user the re-assurance that everything will be a-ok and bring
up a custom dialog of my own.
> However, your best method of handling terminal errors is to design your app
> to avoid them when possible. i.e. Test for the necessary(or guestimated)
> memory before entering memory intensive routines - don't allow entry if
> memory is too low, can't find the DB - generate it yourself but make sure
> your app can handle either 0 records or has a default record to generate.
> Now you should be able to handle terminal errors with the standard method
> because, hopefully they will almost never occur.
you can check out how i do this in the Cube3D sources - which you can
get here. i create a custom form called xmemForm.
http://www.ardiri.com/palm/cube3D/
i believe this issue should be mentioned somewhere in the design
guidelines.. ErrFatalDisplay.. routines are great for debugging :)
(in POSE)
cheers
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
