Just in case anyone cares, I found and fixed this problem, although I still
don't know the actual cause. I finally got enough information to reproduce
it, so I was then able to track it down (using one o' them dee-buggers that
Richard told me about :-).
Necessary conditions:
Call FrmDoDialog,
call FrmAlert before calling FrmDeleteForm on the dialog.
And do this before you've brought up the main form of your application.
Then, the first call to EvtGetEvent will bomb with a fatal error.
Don't ask me why, but that's what happens. Move the
FrmDoDialog--FrmAlert--FrmDeleteForm calls to a place after the main form
has been shown, and everything's fine. Or, move the FrmAlert call to after
the FrmDeleteForm call, and everything's fine. But the combination of
showing an alert after showing a dialog (and before deleting the dialog's
form) with no other forms showing leaves something hanging around that later
causes EvtGetEvent to bomb. Weird, huh?
--Jim Preston
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
