Peter Epstein wrote:
>
> I think I ran into this same problem several years ago. I had an about
> dialog that I presented when the app was first run. When the dialog was
> closed, I used FrmReturnToForm. At first, I had this full screen dialog open
> right away, but this caused problems when clos
I think I ran into this same problem several years ago. I had an about
dialog that I presented when the app was first run. When the dialog was
closed, I used FrmReturnToForm. At first, I had this full screen dialog open
right away, but this caused problems when closing the about dialog. So, I
chan
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 F
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
bypa
If you go into an event loop without having a form, there can be a
crash. It shows up easily on a Clie, but can happen on a "normal"
device, too. For instance, if an Alarm pops up over your app/event-loop
at reset-time.
(Interesting things can also happen with 3rd party Launchers that
release the
