Ben,
Be aware that you can keep the user from triggering the Find command from
your event loop, but if you use FrmDoDialog you loose control since it has
its own event loop. At least they won't be able to exit the application if
you capture the appStopEvent. Also FrmAlert has its own loop. For dialogs, I
ended up writing my own MyDoDialog function, but I haven't done anything
about the alert problem yet since it isn't quite as obnoxious as with the
dialogs.
Along with capturing the Find character, our app also captures the hardware
buttons, calculator button, launch button, menu button, keyboard dots (we
have our own specialized keyboard in our app), HotSync buttons, etc. The
event loop continues until appStopEvent, but only if a global variable
called gbAllowExit is true. That allows me to only let the user out of the
application if they hit the Applications button. In the original spec, there
wasn't even that way out of the app. This would normally be horrible
behavior for a shrink-wrap PalmOS app, but in the case of certain vertical
market solutions, it is a necessary evil; the PalmOS device becomes the
application.
Best of luck...
--
Geoff Shepherd
[EMAIL PROTECTED]
http://www.haytonsystems.com
----- Original Message -----
From: B. Flaumenhaft <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 16, 1999 2:12 PM
Subject: Re: Possible to disable find?
>
> Folks - Thanks for the tips. This is the obvious solution, I don't know
why
> it didn't occur to me already.
>
> Regards,
> Ben Flaumenhaft
>
> >Ben, Don't call SysHandleEvent if the event is a keyEvent with the chr ==
> >findChr and the commandKeyMask is set in the modifiers.
>
>
>
>
