Re: Proposed Accessibility implementation change in Carbon
Re: Proposed Accessibility implementation change in Carbon
- Subject: Re: Proposed Accessibility implementation change in Carbon
- From: David Niemeijer <email@hidden>
- Date: Mon, 27 Oct 2003 19:41:22 +0100
At 10:39 -0700 27/10/03, Guy Fullerton wrote:
> 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.
Ok, thanks and keep up the great AX work!
david.
_______________________________________________
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.