Re: Setting AXDescription from a nib
Re: Setting AXDescription from a nib
- Subject: Re: Setting AXDescription from a nib
- From: Mike Engber <email@hidden>
- Date: Wed, 23 Dec 2009 10:07:54 -0800
First, using the AX APIs on your own app isn't "safe." It might work
for now, but know it's not officially supported. E.g. some day you
might run into deadlock.
On Dec 23, 2009, at 7:05 AM, Avi Drissman wrote:
That sounds like the element would need to be on-screen. That's a
problem, as this would be happening at nib-loading time (this is a
view being extracted from a nib) before it's displayed on-screen.
AXUIElementCopyElementAtPosition is not the only way to access an
element. You could walk your hierarchy to find the element which
seems, to me, to be less fragile than hard coding in screen
coordinates, but still very tedious. However, windows don't show up in
the hierarchy unless they're on-screen - so this may not end up being
any better.
You should file a bug requesting a way to get the overridden values.
In the mean time, I think the best you can do is create an IB outlet
for each element that needs localization and do something like keying
your translations off the outlet name.
-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