-----Original Message-----
From: John Marshall [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 8 January 2002 6:49 AM
To: Palm Developer Forum
Subject: Re: Custom events: possible PalmOS 3.5 bug?
> this bug
> occurs on 3.5.x when MenuHandleEvent is given any kind of event which
> has datum[0] set to 262, and that any other value of datum[0] is safe.
Hi John
This is a really bad bug, and unfortunately your suggestions might not fix
the problem completely. Here are only few examples where
keyDownEventType.chr clashes:
GenericEventType: datum[0..1] // causing David's problem
PenUpEventType: start.x (Coord or Int16)
WinEnterEventType: enterWindow (WinHandle)
WinExitEventType: enterWindow
With start.x there souldn't be a problem in a regular Palm, but it probably
will be with CLIE(some CLIE models have PalmOS 3.5) where a coordinate can
be up to 319. With WindHandle, this is really bizzaire.
How about the following: if PalmOS is 3.5.x, any event with eventType !=
keyDownEvent, and keyDownEventType.chr==262 is not passed to MenuHandleEvent
? This might be safer.
Michael
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
