NSWindowController doc states that you should invoke super's initWithWindow: or initWithWindowNibName:
"In your class’s initialization method, be sure to invoke on super either one of the initWithWindowNibName:... initializers or the initWithWindow: initializer" This breaks the designated initializer pattern, which is bad (and indeed initWithWindowNibName: calls [self initWithWindow:]). Not catastrophic though if you look at the usual usage pattern for NSWindowController. -- Julien On Sat, Oct 30, 2010 at 10:32 PM, Richard Somers <[email protected] > wrote: > Thanks for the insight. > > If calling any of super's initializers will work from the designated > initializer, why then does Apple specifically say the designated initializer > "should begin by sending a message to super to invoke the designated > initializer of its superclass"? > > There must be a subtle issue here. > > --Richard Somers > > > On Oct 30, 2010, at 1:12 PM, Dave Carrigan wrote: > > So just because a designated initializer didn't call super's designated >> initializer, it doesn't mean that super's designated initialer was not >> invoked; it was. >> > > _______________________________________________ > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/jjalon%40gmail.com > > This email sent to [email protected] > _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
