The gist is that you have to remove those certain OS functions (like alert
windows), from your code completely, or from the part that you're trying to
control. That's the only way I've found around it. I think it boils down
to trading ease of use (i.e., programming use) for control.
Regards,
Steve
> -----Original Message-----
> From: Stringer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 24, 2000 10:38 AM
> To: Palm Developer Forum
> Subject: Hard button events
>
>
> I'd like to echo this request.
>
> It has been raised several times on the forum, but I've never seen
> a good response!
>
> The (common) suggestion to trap the key in your main event loop
> has been identified as bogus because certain OS functions, such as
> the alert windows, have their own event loops.
>
> Is there a rock solid way of trapping these button presses?
>
> Because to trap something some of the time is worse than not
> trapping it at all!
>
> Roger Stringer
> Marietta Systems, Inc.
>
> -------------------------------------------------------------
>
> >Subject: Hard button events
> >From: "Anson, Gary" <[EMAIL PROTECTED]>
> >Date: Wed, 23 Feb 2000 09:09:52 -0800
>
> >I was also wondering how to determine if one of the hard
> buttons is pressed
> >and then released to be able to recognise the release?
>
>
> --
> For information on using the Palm Developer Forums, or to
> unsubscribe, please see http://www.palm.com/devzone/mailinglists.html
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
