At 09:59 AM 8/30/2002 +1000, you wrote: >I am calling FrmGotoForm(FormB) to switch from FormA to FormB. >In the frmCloseEvent handler of FormA I'm calling FrmAlert to check if the >user wishes to save the currently open file to flash. >The problem is that the FrmAlert event loop eats the frmLoad and frmOpen >events for FormB. >Once the Alert closes, I'm stuck without an open form. >There are ways around the problem, >I'm just surprised that I haven't come across this in the docs, has anybody >else?.
In general, Palm OS wasn't designed for "confirmation dialogs". The idea is that changes are immediate, so there's no point about asking to save, since the data has already been modified. "Undo" is provided to let you fix something done by mistake. With VFS and flash, this isn't always practical. For this, I'd suggest routing any action that could leave Form A through a "conditional FrmGotoForm" routine that would do the query first, and then issue the FrmGotoForm. -- Ben Combee <[EMAIL PROTECTED]> CodeWarrior for Palm OS technical lead Palm OS programming help @ www.palmoswerks.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
