Here's something else I uncovered on the topic as I played with this
last night:
If you don't activate your own form, you inherit the menu system of
whatever is launched from you. For example, if the user selects "Find"
and then cancels, then my application is suddenly blessed with the Find
Menu. :)
So I'd file this one under the "don't even try it" category.
- Jeff
John Marshall wrote:
>
> DIAMOND JEFF <[EMAIL PROTECTED]> wrote:
> > BUT -> when the user hits the 123 or abc buttons, [...] it crashes hard
> [...]
> > The ONLY thing non standard about my situation is that I have not yet
> > activated my main form,
> [...]
> > Any ideas as to why this is crashing?
>
> I think you answered your own question. :-)
>
> Similarly, I have a bunch of tiny test programs where I do some stuff,
> don't bother putting up a form, and then wait for an appStopEvent so I
> can see what happened.
>
> They correctly ignore graffiti scribbling and the menu button, and
> correctly handle the apps, calc, and even find buttons. But, as you
> say, (on 3.5) the 123 and abc buttons crash it. Bummer.
>
> AFAICT it's not particularly guaranteed that things will work when
> there's no form up, but that doesn't mean they should break gratuitously:
> you might not expect FrmDispatchEvent to work well, but SysHandleEvent
> ought to.
>
> There's code in SysKeyboardDialog that's supposed to handle this case,
> but it doesn't work. I'll file a bug.
>
> John
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
