You may have to catch these key events in your main event loop before
calling SysHandleEvent. I suspect that SysHandleEvent absorbs the key event
(i.e. it returns true so that your form handler is never called), and places
the appStopEvent on the queue.
Eric W. Sirko
Softworks Solutions, LLC
"Vijay Raghavan" <[EMAIL PROTECTED]> wrote in message
news:51331@palm-dev-forum...
>
> 1. Yes I have returned true value
> 2. I am able to handle the silk screen and hard key down events in the
event handler of the form and do nothing in that , but still the application
quits and responds to Launcher and Calculator and other hard keys.
> I have pre-empted the System handling the events like this
> if (bFormOPen==true)
> // Don't give the system a chance to handle the event.
> FrmDispatchEvent(&event);
> if (! SysHandleEvent(&event))
> :
> :
> While debugging I found that the application quits in the while-do loop
of the event loop as the condition 'while (event.eType != appStopEvent);' is
met as soon as the hard/silk Buttons are pressed
> Probably because the launcher applications etc send appStopEvent before
launching?
> 3. I have gone thru the article
http://oasis.palm.com/dev/kb/papers/1148.cfm
> but still don't know why my appl quits.
> thanks a lot in anticipation
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
