Re: explosion when invisible element count is large
Re: explosion when invisible element count is large
- Subject: Re: explosion when invisible element count is large
- From: "Ian Archer" <email@hidden>
- Date: Wed, 24 Jan 2007 21:59:15 -0500
Hmm ... is it wrong to assume that children are sorted according to visibility?
I was thinking of applying a binary search technique, where I find the
start by searching for the first visible element in the array using
BST and similarly to find the last index, then to grab that range.
This system wouldn't work if visibility is arbitrary along the array.
Anyone know this one?
On 12/4/06, Mike Engber <email@hidden> wrote:
On Dec 4, 2006, at 2:07 PM, Ian Archer wrote:
> Does anyone know what I can do?
Use these two calls:
extern AXError AXUIElementGetAttributeValueCount (AXUIElementRef
element, CFStringRef attribute, CFIndex *count);
extern AXError AXUIElementCopyAttributeValues (AXUIElementRef
element, CFStringRef attribute, CFIndex index, CFIndex maxValues,
CFArrayRef *values);
You can use them for any array-valued attribute that you fear might
be be very large. E.g. AXChildren.
As for determining what is actually visible, in the absence of
attributes like AXVisibleRow, you're on your own to test the bounds.
Not a particularly convenient or foolproof technique, but I can't
think of anything better.
-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