>Alan Jay Weiner wrote:
>>
>> There's probably an easier way, but one way that comes to mind is to test for
>> penDown events immediately after you call EvtGetEvent.
>>
>> [web-clipped]
>>
>> if ((event.eType == penDown) &&
>> (event.screenX > 135) &&
>> (event.screenY > 190)) {
>
Then Daniel McCarty added:
> If you're going to hardcode the constants you can easily use
>the #defines from hardware.h:
> #define hwrFindBtnLeft 133
> #define hwrFindBtnTop (hwrSystemTop+hwrCalcBtnHeight)
Completely agree!
I wrote that on-the-fly; I should've taken the time to check for definitions in
the headers...
Thanks for adding them!
And, Ben - For disabling the Find dialog, I'd be more inclined to trap the
findChr as Dan suggest, rather than test the penDown events. Testing penDown
allows you to disable any particular part of the screen...
- Al -
--
-- Alan Weiner -- [EMAIL PROTECTED] -- http://www.ajw.com
