I finally solved this problem: I was calling FrmAlert when I had received the frmCloseEvent to ask whether to save chan- ges or not, and that was what was disrupting the normal flow of events. Now I've removed the option, and as the user can delete the order later, or review it and edit it, I think is more Zen than before. -- Juan de Dios Santander Vela Palm OS Developer Control In Situ, S.L. [EMAIL PROTECTED] ----- Original Message ----- From: "Juan de Dios Santander Vela" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Wednesday, May 30, 2001 1:01 PM Subject: Is this normal behaviour after FrmGotoForm? > OK, I've researched a bit more, and found the following: > > - Indeed, the "handler" member of a FormType has the > address of the event handler function, but this has > been of no use because.... > > - When I receive the frmCloseEvent, FrmGetActiveForm > returns a pointer to a FormType consistent with the > form we're leaving, i.e., the FormID is the expected > one. > > - After that, when I receive the winExitEvent, > FrmGetActiveForm returns NULL, and from that moment > on, I only get NULL from it... and no winEnter or > frmLoad/frmOpen events for the form FrmGotoForm > posted... > > I still have to research if this behaviour is shown > on the real device, now I'm getting it with a Palm Vx > ROM transfered to POSE 3.06 (I had to switch to it > in order to be able to debug with a Symbol 1700 ROM). -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
