Re: NSView nextResponder always the viewController?
Re: NSView nextResponder always the viewController?
- Subject: Re: NSView nextResponder always the viewController?
- From: Gordon Apple <email@hidden>
- Date: Wed, 17 Dec 2014 11:01:06 -0500
- Thread-topic: NSView nextResponder always the viewController?
Thanks, I¹ll look into that.
It would have been nice if the docs has more explanation of how they are
handling the responder chain for viewControllers. Also, it appears that the
view is now holding a reference to the viewController (when used). However,
it is not public. I wish that would make that reference available, at least
as read-only. That would simplify access for other controllers which need
the reference back to the viewController instead of having to use separate
connected outlets.
We are not intercepting any actions in the viewController, so we changed the
insertions to come after the viewController instead of after the view. No
more infinite loops.
Back in the MacApp days, we had something called ³Behaviors² which could be
added into the responder chain. I had some articles published in the MacApp
journal on using these to handle individual actions like copy, paste, drag,
drop, selections, etc. It looks like at least some of these could now be
handled with custom gesture recognizers.
On 12/17/14 12:09 AM, "email@hidden"
<email@hidden> wrote:
> I don't know the answer to that, but even before 10.10 I had problems with
> inserting responders and found that 10.7's supplementalTargetForAction:sender:
> did everything I needed insertion for. If that works for what you need it's so
> much easier to manage.
_______________________________________________
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