Re: Should I remove NSTabViews from the hierarchy?
Re: Should I remove NSTabViews from the hierarchy?
- Subject: Re: Should I remove NSTabViews from the hierarchy?
- From: Ricky Sharp <email@hidden>
- Date: Sat, 24 Feb 2007 13:43:09 -0600
On Feb 22, 2007, at 6:47 PM, Ricky Sharp wrote:
Thanks James, this really helps out a lot. I'll keep the deep
hierarchy as-is. I suppose I could always add an attribute (e.g.
title) at some point to the groups so that they can be referred to
either by index or name.
Just tried an experiment. I subclassed NSTabView in order to add a
title_II** attribute. My end goal was to then provide a 'title'
accessibility attribute that would reference that ivar and I could
thus have names for groups.
I modified my custom IB palette to contain the subclass, created a
test nib and inspected it with Prefab UI browser and Apple's tools.
Strange things occurred with regards to the children attribute.
If I use a standard NSTabView either with tabs, or tabless, both
inspection apps give me proper attributes. Children is always a non-
empty array with appropriate number of items (i.e. NSTabViewItem
instances)
When I use my subclass (IITabView), if I have tabs, then all is
well. However, when I set it to be tabless, both inspection apps
report that children is an empty array.
A workaround is of course to provide my own implementation for the
children attribute, but why wouldn't I inherit the one from NSTabView?
Currently, I don't override anything in terms of accessibility. My
NSTabView subclass simply overrides initWithFrame, initWithCoder,
encodeWithCoder and dealloc in order to work with the additional
title_II ivar. And, I always call through to super in all cases.
I can file a bug if need be.
** I prefix/suffix ivars, methods, et. al. in order to have a unique
namespace.
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
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