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: Fri, 26 Jan 2007 20:20:47 -0500
For example, a sample documentation page from Apple's site has
thousands of child elements containing the components of the page,
which itself spans many, many scroll lengths (i.e. a scroll amount
which would move the entirety of a given span of content out of view).
In this case, traversing the group members requires a huge amount of
processing and copying (it takes my Core 2 duo machine up to 99% CPU
for 10 seconds for the single page). It is simply impractical for me
to traverse the widgets.
On 1/26/07, James Dempsey <email@hidden> wrote:
On Jan 26, 2007, at 3:50 PM, Ian Archer
wrote:
Without this order guarantee, there seems to be no way to limit a
hierarchy traversal. Consequently, a traversal can always have the
potential to explode when components have a large but practical number
of children.
According to the documentation, AXVisibleChildren attribute should be
used for scroll views and other components which can have children
scrolled out of view. As far as I can tell, there is no Apple widget
which supports this feature, which (at least, according to me) is
essential for any application which ever applies a hierarchy
traversal.
Could this be considered grounds for a bug report?
Definitely file a bug - but please call
out the particular cases you are seeing.
There are a number of UI elements that use
AXVisibleChildren or a similar 'visible'
attribute.
AXList, AXRow, AXMenuBar, AXMenu, and AXRadioGroup
have a visible children
attribute.
AXTable, AXOutline provide a list of
visible rows.
AXTable, AXOutline, and AXBrowser provide
a list of visible columns.
So, I think for many cases of UI Elements
that can contain a large number of
children this is already in place.
Note also that it is not the scroll view
that would have this property - for
instance a scroll view contains a table
view, it is the table that has the many
rows.
What is the particular case that you are
looking at?
-James
--------------------------------------------------
James Dempsey
AppKit Engineering
Apple
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