>>
>> [long "arguetecting" (?) session web-clipped...]
Arguetecting is a term a friend of mine coined - it refers to sitting around and
arguing and brainstorming about how something does or should work...
(one of my favorite activities, btw... :)
>> Naturally, I'm showing Fitaly processing the events "just so" the errors make
>> sense; there can be some jitter in the above sequence and failures still occur
>> properly - I don't have any way to track the processing and pen activity quite
>> that closely... (darn! I wish I could trap the pen enqueuing! :)
>
> Methinks one easy way around this is would be to hold input until the
>pen is released, a la
>
> case penDown:
> do
> EvtGetPen(&penX, &penY, &penDown);
> while (penDown);
>
>This way you're assured that the penDown and penUp x, y coordinates that
>you receive are the latest and greatest, and you don't have to rely on
>pulling them out of the pen queue.
The code used to do this. I switched it to using the coordinates from the pen
events. It didn't make a bit of difference...
EvtGetPen can only exacerbate the problem. It passes back the last-known pen
position, so if there are rapid taps, it could miss some of the positions.
For example:
event 1: pen down
event 2: pen up
Fitaly gets event 1, calls EvtGetPen and gets the proper pen-down coordinate
event 3: pen down somewhere else
Fitaly gets event 2, calls EvtGetPen bug gets event 3's position rather than
event 2's position.
> BTW, how does a user cancel an input letter if dragging off the letter
>now capitalizes it?
um... I guess they backspace over the error... :)
> (p.s. You may want to preface a 15K post with "long" somewhere in the
>subject to keep list members happy. ;)
yes; I apologize for this! I had intended to put "(long)" in the subject line,
and then forgot to do so.
- Al -
--
-- Alan Weiner -- [EMAIL PROTECTED] -- http://www.ajw.com
