Re: Does AXObserverRemoveNotification work?
Re: Does AXObserverRemoveNotification work?
- Subject: Re: Does AXObserverRemoveNotification work?
- From: Andrew Taylor <email@hidden>
- Date: Tue, 19 Nov 2002 07:17:18 -0500
At 7:53 PM -0500 11/18/02, Bill Cheeseman wrote:
on 02-11-18 7:44 PM, Eric Schlegel at email@hidden wrote:
On Monday, November 18, 2002, at 01:17 PM, Bill Cheeseman wrote:
When I call AXObserverRemoveNotification in my assistive app, the
target
application unexpectedly quits, and the function generates a
kAXErrorCannotComplete error.
This is a known bug in the Carbon accessibility implementation which
will be fixed in an upcoming software update.
There's no workaround other than just not calling
AXObserverRemoveNotification.
How about releasing the observer and starting over with a new one? It means
giving up any other notifications that have been registered with that
observer, of course, but I could write a routine to remember them and
reinstate them with a new observer. Just wondering if you know if it would
work, before I invest any time in it.
Actually there is yet another manifestation of this bug, if your
application quits with observers registered, there will be lots more
crashes - all the observed applications will crash as they attempt to
notify your no longer present application of observed events.
The work around is to create a background application that once
launched does not quit. Have that application do all the observer
registration and have it communicate with your main application
through Carbon events or CFMessagePort or AppleEvents or other means.
So if you have to ship before Apple can release the fix, the above
will do it. It will also allow you to just continue testing your code
without extra crashes.
_______________________________________________
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.