Re: Meaning of log message: Unable to create AX specifier for element
Re: Meaning of log message: Unable to create AX specifier for element
- Subject: Re: Meaning of log message: Unable to create AX specifier for element
- From: Ray Fischer <email@hidden>
- Date: Mon, 26 Sep 2005 19:54:27 -0700
- Thread-topic: Meaning of log message: Unable to create AX specifier for element
On 9/26/05 9:04 AM, "Mike Engber" <email@hidden> wrote:
>> Can somebody tell me what this console message means and why it's
>> happening?
>> "Unable to create AX specifier for element:"
>
> What are you using to exercise the accessibility - Accessibility
> Inspector ?
Actually its prior incarnation - UIElementInspector
> It could be the UIElementRef your trying to use is for a UI Element
> that has been
> destroyed. Is the hierarchy changing while you navigate it?
>
> If it's not that, then it most likely it means an asymmetry in the
> parent-child hierarchy.
> The problematic UI Element is being (unsuccessfully) looked for in
> the children list
> of its parent (whatever UI Element it reports as the value of its
> parent attribute).
That was it. With that useful hint I was able to track down the problem.
Now onto the next problem.
Thanks.
>> This is Cocoa accessibility code that I'm trying to get working.
>> The message
>> occurs when I have NSAccessibilityDebugLogLevel set to 3.
>
> 3? Why 3. I don't suggest using anything but 1.
TN2124 says 3 is the maximum value and I wanted the most information.
-------------
Ray Fischer
_______________________________________________
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