If you choose to use explicit window controllers, they should own the window they load. That's what they're for. You might customize them with a protocol on the document controller as a kind of delegate for the window controllers to give a simple callback API that is decoupled. This pattern is rich in Cocoa. A little boilerplate goes a long way.
Sent from my iPhone > On Jun 10, 2016, at 10:16 PM, Daryle Walker <dary...@mac.com> wrote: > > I replaced windowNibName with makeWindowControllers since I'm moving window > management to a separate controller. I kept windowControllerDidLoadNib > around. Now I wondered if it still gets called. I put in a "print( #function > + "got called." )" and never saw the output. Is this method called only when > the default NIB-in-NSDocument strategy is used? (And so I can remove it in > my app.) > > Sent from my iPhone > _______________________________________________ > > 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/dangerwillrobinsondanger%40gmail.com > > This email sent to dangerwillrobinsondan...@gmail.com _______________________________________________ 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
