Oh, gosh, Peter. This ought to teach me to write notes a week of
low-sleep after the fact. Confused ramblings about "reset-time": Yes,
it's reset-time in a global sense, but certainly not under the reset
launch code. :)
So, I just looked at the code. Here's the deal: Call FrmReturnToForm()
when FrmGetActiveForm() will return a NULL. This call can be made if
someone has not set an active form, but does get an event and send it to
SysHandleEvent(). DateBook's alarm routine make the FrmReturnToForm()
call, for instance.
Granted, it's not easy to get this problem. So, I figured it was best to
leave a note somewhere in "the archives" in case anyone else hits the
situation. Or in case someone who happened to be editting the source
code wanted to put an assert or "return;" in to the code.
Alex
Peter Epstein wrote:
>
> I don't think it's kosher to present any dialog in response to the reset
> notification launch code. Also, if you don't set up a current form in your
> application, I don't think you're allowed to pop up dialogs either. Either
> you use the form manager or not. If you want to do your own thing, and
> bypass it, that's fine, but you can't expect it to work properly for dialogs
> if you don't give it a chance to manage what's on the screen before the
> dialog opens. I could be wrong about this, but that's what I think.
> --
> Peter Epstein
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
