That's what I'm currently doing. There are several actions that can cause the FormA => FormB transition and the frmCloseEvent handler seemed the most appropriate place. Now I have a function which does the Alert and then calls FrmGotoForm.
KP "Steve Mann" <[EMAIL PROTECTED]> wrote in message news:94632@palm-dev-forum... > > >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. > > Why not do the FrmAlert in whatever code precedes the FrmGotoForm > instead of follows it. There must be some kind of action that > triggers the FrmGotoForm. > > Regards, > Steve Mann > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
