Re: NSWindowController and designated initializer rules
Re: NSWindowController and designated initializer rules
- Subject: Re: NSWindowController and designated initializer rules
- From: Sean McBride <email@hidden>
- Date: Tue, 24 Jun 2014 10:55:58 -0400
- Organization: Rogue Research Inc.
On Mon, 23 Jun 2014 18:14:05 -0700, Quincey Morris said:
>In that regard, ‘initWithWindowNibName:’ must be a designated
>initializer, since subclasses that don’t do their own nib loading have
>nothing else to call “up” to.
>
>I assume, therefore, that ‘initWithWindowNibName:’ is marked as a
>designated initializer in 10.10, though I haven’t looked to check this.
This was the real point of my question, though I was trying not to mention 10.10 due to any NDA (though Apple seems more lax about it recently)[1].
But Roland has already spilt the beans :) and showed us that the 10.10 SDK does not tag initWithWindowNibName: with NS_DESIGNATED_INITIALIZER. I guess it's omission could be a bug, but assuming not, Sketch gets a compiler warning if you tag its own designated initializer (init) with NS_DESIGNATED_INITIALIZER, since it doesn't call one of super's designated initializers.
[1] I tried asking on the "dev forums", but there don't seem to be any developers there, just end users with install problems mostly. :(
Cheers,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden