If you create you're own alert dialogs, you can always trap any event you don't want passed on to the OS. As it was pointed out, alerts have their own event handler.
----- Original Message ----- From: "Laurens" <[EMAIL PROTECTED]> Newsgroups: palm-dev-forum To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Monday, December 15, 2003 5:10 PM Subject: Re: Capture Keys > > "rguevara" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > With this blockade the calc, find, launch buttons and hard keys when I am > in the forms listed previously. but not like blocking > > them when I am in the alert forms. > > When you display alerts with FrmAlert/FrmCustomAlert, events are handled > locally by a custom event loop (inside the function itself) and never reach > your main event loop. That's why FrmAlert blocks until the alert is > dismissed. > > The only solution I can of is to set the Creator IDs of the silkscreen > buttons to that of your app and restore them when the application exits. (I > assume you want to prevent the user from exiting your application.) > > > Regards > -Laurens > > > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
