Re: Accessibility issues with NSPopover
Re: Accessibility issues with NSPopover
- Subject: Re: Accessibility issues with NSPopover
- From: Kyle Sluder <email@hidden>
- Date: Wed, 09 May 2012 08:55:43 -0700
On May 9, 2012, at 5:16 AM, Motti Shneor <email@hidden> wrote:
> 3. As NSPopover manages its internal window in a very-opaque way, I can't find a way THAT WORKS to set up the "initialFirstResponder", or window title, or any accessibility attributes on the popover window.
Can you override -viewDidMoveToWindow in the appropriate view to set the initialFirstResponder on self.window? I agree this is pretty hackish; NSPopover should expose initialFirstResponder directly. (Actually, NSViewController should probably do that, because anywhere you're adding and removing view controllers you're likely going to want to make the appropriate view first responder.)
>
> 4. I was not able to set up accessibility link from anywhere else in my application to the popoever (or one of its subviews).
>
> There is very little documentation and help on NSPopovers, and to say the truth, it breaks Apple's most basic Cocoa design. NSPopover is neither Model, View or Controller. I wonder...
>
I wouldn't go this far. I look at NSPopover like NSWindowController. Of course you don't have access to the actual window that displays the popover, but the same was true for NSDrawer.
At first I didn't understand why NSPopover wasn't itself a subclass of NSViewController, but it makes sense that you might want to use NSPopover to display pieces of your interface that can appear both within the popover and in other places—like torn off in a floating window. Then the architecture of NSPopover starts to make mote sense.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden