Hi Kyle,
We are in agreement that the piece I was missing was the call to
addWindowController. I was perhaps a bit sloppy when I said that the nib file
was in the responder chain versus the nswindowcontroller. But my whole point
was to understand how the responder chain works in a document-based application
across different nibs -- which wasn't clear to me from the docs or the archives.
Jason
----- Original Message ----
> From: Kyle Sluder <kyle.slu...@gmail.com>
> To: Jason Bruce <jasonwbr...@yahoo.com>
> Cc: cocoa-dev@lists.apple.com
> Sent: Tue, August 3, 2010 7:00:52 PM
> Subject: Re: Need help understanding first responder and multiple nibs
>
> On Tue, Aug 3, 2010 at 4:50 PM, Jason Bruce <jasonwbr...@yahoo.com> wrote:
> > After thinking about this for awhile, it's all starting to make sense. In
> >
>order
> > to place associate an nswindowcontroller with a document, you just have to
>call
> > addwindowController after you create the additional nswindowcontroller.
> This
> > will place the secondary nib file in the document's responder chain, so
>there
> > will be no need to pass in a reference to the document to the secondary
>window
> > controller, and no need to call an action in the window controller.
>
> No, your reasoning is still wrong. Nib files aren't things that can be
> in the responder chain. The responder chain isn't magically aware of
> nib files; it simply follows the links described in the documentation,
> starting from the key window.
>
> Your bug was that you weren't calling -[NSDocument
> addWindowController:]. -addWindowController: calls -setDocument: on
> the window controller, thus doing exactly what you said you didn't
> think you had to do.
>
> --Kyle Sluder
>
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
