Re: Proposed Accessibility implementation change in Carbon
Re: Proposed Accessibility implementation change in Carbon
- Subject: Re: Proposed Accessibility implementation change in Carbon
- From: Guy Fullerton <email@hidden>
- Date: Mon, 27 Oct 2003 10:39:12 -0700
On 10/26/03 11:43 PM, "David Niemeijer" <email@hidden> wrote:
>
At 12:01 -0800 26/10/03, Guy Fullerton wrote:
>
> The issue is that an AXUIElement may effectively say that it does not
>
> support the AXChildrenAttribute even though it really *does* support that
>
> attribute. I'm not sure how an existing fallback capability could deal with
>
> this unless the fallback capability always asked for AXChildren regardless
>
> of whether the UIElement reported it via AXUIElementCopyAttributeNames.
>
>
>
> (The same thing goes for AXParentAttribute.)
>
>
When I am exploring the AX hierarchy I tend to ask for the
>
AXChildrenAttribute without even calling
>
AXUIElementCopyAttributeNames. Then I check for an error. If there is
>
no error I proceed to check whether I have an empty array or not. Is
>
there any reason not to do it this way?
That's an excellent way to do it. It's very proactive, and would certainly
avoid the situation I was describing.
>
Are there other
>
cases where AXUIElementCopyAttributeNames may report wrongly and just
>
asking for an attribute and checking for an error might be better?
I can't think of any off the top of my head.
_______________________________________________
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.