Re: Bugs Involving Input Components Still Open in Radar
Re: Bugs Involving Input Components Still Open in Radar
- Subject: Re: Bugs Involving Input Components Still Open in Radar
- From: Eric Schlegel <email@hidden>
- Date: Wed, 17 Aug 2005 08:47:41 -0700
On Aug 17, 2005, at 7:53 AM, David Niemeijer wrote:
At 0:26 -0400 1/8/05, Maurice Volaski wrote:
> Have you tried using the CG remote operation stuff? See
CGRemoteOperation.h for details. It's how Remote Desktop, VNC,
etc, do
their stuff. It's certainly a better place to look than either the
accessibility stuff ( which the use can turn off or your app
needs to
be trusted ) or patching window server functions.
AXUIElementPostKeyboardEvent and CGPostKeyboardEvent are the same
call
internally. They both suffer from radar bug 4107468.
what is that bug about?
It mentions that using AXUIElementPostKeyboardEvent and
CGPostKeyboardEvent will both cause local user input events to be
inhibited for some time after the APIs have been used to post
keyboard events. Apparently, this is by design; CGPostKeyboardEvent
has worked this way since 10.0 and can't be changed without breaking
other apps that depend on this behavior.
On Tiger, you can use the CGEventRef APIs, which do not inhibit local
events. It may also be possible to use CGInhibitLocalEvents or
CGSetLocalEventsSuppressionInterval to prevent the inhibiting behavior.
-eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden