Re: Determining whether a window supports accessibility
Re: Determining whether a window supports accessibility
- Subject: Re: Determining whether a window supports accessibility
- From: Mike Engber <email@hidden>
- Date: Thu, 2 Jun 2005 09:07:17 -0700
In a sense, what you're asking is "How can I discover if a window
contains UIElements that aren't exposed via the Accessibility APIs?"
Clearly, this cannot be answered by Accessibility APIs.
As someone already pointed out, you can take a guess by asking the
window for its children. If there are none (apart the standard window
controls), that's pretty suspicious. On the other hand it could just
be an empty window. There is no way to tell for sure just using the
Accessibility APIs.
If you don't limit yourself to the Accessibility APIs, then there are
other possibilities for detecting the problem. E.g. if the app
supports AppleScript you could see if what AppleScript has to say
about the window matches what the Accessibility APIs report. Note,
AppleScript GUI scripting is built on top of the Accessibility APIs,
so using that won't accomplish anything.
-ME
On Jun 2, 2005, at 6:32 AM, David Niemeijer wrote:
Is there a way (a logic basically based on interpretting the AX
features) that would allow me to determine whether a Window
implements AX features or not.
For example, when I point my cursor at the center of a Word
document window UIElement Inspector tells me that the cursor is
above an AXWindow. If I do the same for TextEdit it tells me I am
above an AXTextArea. However, if I move my cursor over the window
titlebar of the TextEdit window UI Element Inspector also tells me
it is an AXWindow. In the Word case everything in the window but
the scrollbars and grow area are reported as AXWindow (in other
words the Window does not fully implement AX features). In the
TextEdit case I only get reported AXWindow over the titlebar. Is
there a way to distinguish the TextEdit titlebar's AXWindow
reporting from the entire Word window AXWindow reporting? You see,
I need to deal with things differently in the case of a click in a
window that everywhere just reports as AXWindow from the case of a
window where AX is fully implemented and the click was just in the
window frame. Or, framing my question differently, is there a way
to recognize a window that is entirely report as a window frame
(The Word case) from one where only the real frame is rported as a
frame (the TextEdit case)?
Thanks,
david.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (Accessibility-
email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
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