I am building an OS X NSDocument app with a fairly complex view hierarchy and want to interpose my view controllers into the responder chain (this I can do). Some of the displayed views will feature just a button (to enable creation of a new object). This means that the first responder will be the window itself (I don't really want to change the default NSButton firstResponder refusal behaviour).
My intention is track the status of my top level view controllers and insert/remove these as required in the responder chain between the window and the window controller (rather than between views in the chain). That way I figure that actions and validation methods will always hit the view controller regardless of whether an NSView based first responder exists. Is this the best approach? The responder chain used in a particular situation does vary: https://developer.apple.com/library/mac/documentation/cocoa/conceptual/EventOverview/EventArchitecture/EventArchitecture.html#//apple_ref/doc/uid/10000060i-CH3-SW2 Jonathan _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
