Re: Making VoiceOver see changes
Re: Making VoiceOver see changes
- Subject: Re: Making VoiceOver see changes
- From: Mike Engber <email@hidden>
- Date: Thu, 9 Nov 2006 10:34:57 -0800
Yes, descending from NSObject (and not NSView or NSControl) is going
to mean that no one can register for notifications on you.
This is a known issue, but it wouldn't hurt to file a bug on it.
My suggestion to work around this it to use the enclosing view as the
UI Element. You can still keep most of the accessibility logic in
your slider object - just have the NSView forward the appropriate
accessibility calls to it. Just remember - the slider object can
never return itself as a UI Element - it should always return the
enclosing view.
-ME
On Nov 9, 2006, at 9:49 AM, Michael Ash wrote:
On Nov 9, 2006, at 12:30 PM, Mike Engber wrote:
It seems to me that this is the problem, although I could easily
be wrong. How can I make my custom UI element observable?
What's the class hierarchy of your control? If it's a descendant
of NSView or NSControl, it should work.
On the other hand if it descends from NSCell there could be some
issues...
It is treated like a cell by its enclosing view, but it is neither
a descendent of NSView nor of NSCell. It's a subclass of another
custom class which in turn inherits directly from NSObject. But I'm
guessing those issues are going to be similar to the ones you
allude to for NSCell, can you elaborate on what those would be?
_______________________________________________
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