Re: NSAccessibilityShownMenuAttribute vs kAXShownMenuUIElementAttribute
Re: NSAccessibilityShownMenuAttribute vs kAXShownMenuUIElementAttribute
- Subject: Re: NSAccessibilityShownMenuAttribute vs kAXShownMenuUIElementAttribute
- From: Bill Cheeseman <email@hidden>
- Date: Mon, 14 Jan 2008 13:15:04 -0500
- Thread-topic: NSAccessibilityShownMenuAttribute vs kAXShownMenuUIElementAttribute
on 2008-01-14 11:07 AM, Dave MacLachlan at email@hidden wrote:
> which are all defined in NSAccessibility.h but missing in the Carbon
> header.
Over the last several years I've brought to Apple's attention a number of
"omissions" of constant declarations from the AX headers vs. the
NSAccessibility headers or vice versa. Sometimes Apple adds a declaration in
response, and sometimes not. In general, my impression is that Apple doesn't
feel a need for a declaration unless the particular item is actually used in
the one API or the other.
In my apps, I use any available constant from whichever header declares it,
with a bias towards the AX header where I'm using AX functions and to the
NSAccessibility header when I'm using Cocoa methods.
But if a constant is declared and never defined, or defined differently
between the two APIs, that certainly seems like a bug!
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
www.quecheesoftware.com
PreFab Software - www.prefabsoftware.com
_______________________________________________
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