Re: accessibility-dev digest, Vol 1 #71 - 3 msgs
Re: accessibility-dev digest, Vol 1 #71 - 3 msgs
- Subject: Re: accessibility-dev digest, Vol 1 #71 - 3 msgs
- From: "Reinder Verlinde" <email@hidden>
- Date: Fri, 14 Feb 2003 08:51:05 +0100
John Louch <email@hidden> wrote:
>
On Thu, 13 Feb 2003, Reinder Verlinde wrote:
>
>> using CGWarpMouseCursorPosition and CGPostMouseEvent
>
>> while zoomed in using the vision-impaired mode causes all kind of
odd
>
>> behaviour, but I suppose that's expected.
>
This is a known bug that will be fixed for the next release.
Hm. If we're lucky that 'next release' just came out. I'll check.
>
CGPostMouseEvent is very light weight. Almost as light as normal
mouse
>
movement using the mouse. You do need to be careful to not flood the
system
>
with events, since you can send mouse events faster than they can be
>
processed.
So, how does one best detect that a mouse move event has been
processed? I can think of several:
- registering a mouse moved handler for the entire screen
- polling to see whether mouse position changed
- querying the event queue
Polling generally is to be avoided, but I am not sure whether the
others will always work (e.g. when your app is not frontmost, or when
the old and/or new position are outside one's window. Or perhaps, once
should create a transparent window that covers all screen(s), and
register a mouse moved handler with that?)
Reinder Verlinde
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.