Re: NSReponder chain and controllers

FROM : Adam Knight
DATE : Thu Jun 19 21:05:04 2008

Add your controllers to the responder chain when appropriate and then 
put the IBAction methods in the relevant controllers.  If you 
duplicate methods (like delete: or cancel:) take care as to what order 
you add them into the chain because the first to respond wins (though 
it can always send it to its next responder if it doesn't make sense 
at the moment, like cancel: without an operation running).

Adam Knight
"Every man is guilty of all the good he didn't do."  -- Voltaire



On Jun 19, 2008, at 1:20 PM, Robert Douglas wrote:

> My code is getting ugly so I suspect I'm doing something wrong.  I'm 
> trying to hook up menu items in my main menu to actions that I've 
> defined in my controllers.  I have a Core Data doc with a multiple 
> master-detail view hierarchy, and for testing purposes have buttons 
> connected to  a wide variety of methods.  The NSArrayController 
> subclasses are not in the responder chain so I'm connecting the menu 
> items to the first responder, catching the action messages in my 
> document and then dispatch them to the correct controller.  That 
> translates into a lot of simple dispatch code.  I could move all the 
> intelligence to the document level but that strikes me as  equally 
> ugly.  Any suggestions?