Gearoid,
I think you can re-map the contrast button and your
workaround should work but I'm looking for a standard
way of handling this and probably an explanation as to
why this happens. In my case, it always takes me to a
particular screen, with FORMID > 1 and crashes.
Anybody has any clue?
-
Come to think of it I'm not sure if you're able to re-map the contrast
button.
From: "Gearoid Murphy" <[EMAIL PROTECTED]>
Reply-To: "Palm Developer Forum" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Subject
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Subject: Re: Handling the contrast button on Palm V and Palm IIIx
Date: Thu, 27 Mar 2003 12:43:31 +0100
Prashant Jha wrote:
But the problem is that it works when we have a
regular form on the screen, but not when we have an
alert box or
Prashant Jha wrote:
But the problem is that it works when we have a
regular form on the screen, but not when we have an
alert box or a date picker on top of the form. This is
the real issue. The application crashes when we press
the contrast adjustment button while there is an alert
box open on top
Ralf,
Thanks for the response but looks like I misled you by
not giving the complete EventLoop code, I am filtering
these events out and not passing them to the
SysHandleEvent(). Here is my EventLoop function -
void EventLoop()
{
EventType event;
do
{
EvtGetEvent( &event, 2000 );
Simply filter these event in your main application loop and don't pass
it to SysHandleEvent():
e.g. AppEventLoop():
EvtGetEvent(&event, evtWaitForever);
// filter out special keys..
if ((event.eType==keyDownEvent) &&
((event.data.keyDown.chr==vchrContrast) ||
(event.data.keyDown.chr==vc
Hi,
I'm using the following code in my EventLoop to handle
the keydown event from the contrast button on Palm V
and Palm IIIx and some symbol devices:
if(( event.eType == keyDownEvent ) and
(EvtKeydownIsVirtual(&event)))
{
//Ignore this event
}
It works fine on regular forms, ie whe
