Re: Subclassing NSView in Yosemite?
Re: Subclassing NSView in Yosemite?
- Subject: Re: Subclassing NSView in Yosemite?
- From: Kyle Sluder <email@hidden>
- Date: Thu, 06 Nov 2014 08:08:06 -0800
On Nov 6, 2014, at 6:29 AM, Alex Hall <email@hidden> wrote:
>
> Hello list,
> I've subclassed NSView before, doing all my setup in init withFrame, and it works fine. Now, though, I'm using Swift in Xcode 6.1 to build a project against 10.10, and I'm getting an error that I need to implement initWithCoder:NSCoder.
>
> The problem is that the documentation says nothing about this, so I'm not sure which initializer is called when. That is, where do I put all my setup to ensure it gets called? I'd rather not do it twice, since I'm afraid one or the other initializer could get called when I don't expect it and set things up as though the app had just launched.
Read the Resource Programming Guide. -initWithCoder: is primarily called when unarchiving a view from a nib.
It’s kind of annoying that Swift makes you implement this method for all views, regardless of whether they’ll be in a nib or not, but it’s the only way the language can back up its safety guarantees.
--Kyle Sluder
_______________________________________________
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