Hi Conrad > On 2 Oct 2015, at 18:35, Conrad Shultz <[email protected]> wrote: > >> >> On Sep 30, 2015, at 9:15 AM, Jonathan Mitchell <[email protected]> >> wrote: >> >> In my app i manage the responder chain on 10.8 and 10.9 to insert the >> NSViewController into the responder chain. >> The view controllers are inserted just below the NSWindowController so that >> designated view controllers can respond to actions coming up the chain from >> any source. >> ie: the NSViewController for any view will NOT be the view’s next responder >> - it will be higher up in the chain. >> >> On 10.10 the view controller is automatically assigned to be the view’s next >> responder. >> I want to override this behaviour to not assign the controller as the view’s >> next responder. >> I thought this would be trivial but once the NSView nextResponder has been >> set to the controller the view seems reluctant to have its next responder >> changed. >> The next responder remains set to the view controller; > > Starting with 10.10, -[NSView setNextResponder:] forwards to the view > controller, which is what you are seeing. > I am not disputing the veracity of the release notes!
The troublesome aspect is that I cannot override this new behaviour. The view will not seemingly permit its nextResponder to be diverted from the NSViewController. I am not aware of anywhere else in app kit where this occurs nor can I really understand why this sticky responder behaviour has been adopted. Normally I can assign the nextResponder as I see fit. I had hoped that whoever coded this new behaviour might chip in… Thanks for the reply. Jonathan _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
