Re: Where does the accessibility hierarchy "start"?
Re: Where does the accessibility hierarchy "start"?
- Subject: Re: Where does the accessibility hierarchy "start"?
- From: Mike Engber <email@hidden>
- Date: Fri, 2 Jun 2006 10:10:26 -0700
Let me correct my previous email:
On Jun 2, 2006, at 10:00 AM, Mike Engber wrote:
In theory, you shouldn't have to subclass NSApp - because it should
delegate stuff like hit testing and AXFocusedUIElement to the
appropriate window.
In practice, it looks like you may have to override NSApp so your
can override AXFocusedUIElement - I think your window's override of
that attribute will be circumvented. This is a bug - I'll file it.
On closer examination, it looks like NSApp _is_ doing the right thing.
So, you shouldn't have to subclass NSApp. If your window overrides
accessibilityFocusedUIElement that should control what the app
returns for its AXFocusedUIElement attribute (when that window has
focus).
There could be other problems that will force you to subclass NSApp,
but I can't think of one - yet.
-ME
_______________________________________________
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