Re: Does AXObserverRemoveNotification work?
Re: Does AXObserverRemoveNotification work?
- Subject: Re: Does AXObserverRemoveNotification work?
- From: Mike Engber <email@hidden>
- Date: Thu, 21 Nov 2002 09:41:32 -0800
Is there any way you can provide a list of what DID change from
10.2.0, to
10.2.1, to 10.2.2? I'm currently writing my stuff on 10.2.1, but I
would
like to include workarounds for any issues in 10.2.0 so it will
function
reliably on 10.2.0 and later. I've got the 10.2.1 issues pretty well
covered
at this point.
Shorter (non) answer:
No changes have been made in Cocoa accessibility - that's not to say
Cocoa apps are unaffected - Cocoa inherits some of its accessibility
from Carbon (e.g. menus).
Also, no changes have been made in the actual Accessibility APIs
themselves.
A few changes were made in Carbon, I'll leave it to some from that team
to enumerate them or, hopefully, just point you at the release notes.
Much longer (non) answer:
A rehash of the accessibility architecture might be helpful at this
point and for future reference since it's easy to get confused about
the various (3) pieces:
Accessibility APIs - This is small library residing in Application
services. Its code is used by assistive apps - these are the public
APIs - AXBlahBlah, ... Other parts of its code are used by the target
apps - unbeknownst to them - these are private APIs. This library is,
for the most part, just a communication layer, passing back and forth
requests for attributes values, etc.
Cocoa Accessibility - This is a protocol (plus some behinds the scenes
machinery) that makes Cocoa objects visible to accessibility. This
protocol is public, but you probably haven't used it, nor will you need
to, unless you have some custom widget that needs to work with
accessibility. The standard Cocoa widgets already implement this
protocol.
Carbon Accessibility - This is the Carbon equivalent to Cocoa's
protocol, Carbon event based instead of method based. Again, it's
public, but you probably haven't messed with it.
Most of the bugs we've been discussing are with Carbon or Cocoa
accessibility. More specifically, with the way the standard widgets
have been (or haven't been) accessorized. I don't think we've found any
bugs in the "Accessibility APIs". If the refcon corruption you reported
had turned out to be real - that _would_ have been a bug in the
"Accessibility APIs."
So, to readdress your initial q, to date, only Carbon Accessibility has
changed in software updates.
-ME
_______________________________________________
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.