> added--... In that case, I get a winExitEvent, a penUpEvent > --that corresponds to the fact the pen was lifted after pre- > ssing the control that initiated the FrmGotoForm--, a nil- > Event... and unless I tap the screen --which by this moment > is blank--, or write some graffiti, I get nothing else, > when I should have received a winEnterEvent, a frmLoadEvent, > and a frmOpenEvent, in my understanding...
So did you (or anyone else) ever figure out what happened? I have somehow just become a victim of this problem. To restate the problem, when switching from form B back to form A (in POSE), the app apparently hangs with a blank screen. In reality it's not hung; it's processing events, and you can still switch to other apps or break into the debugger. The frmLoad event has somehow been sucked up or never got enqueued, which is pretty strange because I've verified that FrmGotoForm was called, and that the frmCloseForm and winExit events got enqueued and processed. The strangest thing is that release ROMs don't show this problem. I can work around it, therefore, but it's kind of frustrating, and I'm paranoid I've missed some critical thing I'm supposed to do or trashed some memory, and the release ROM is just covering it up. I'm going to have to dig farther back through the archives, I guess. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
