Re: initWithCoder in Nib object loading
Re: initWithCoder in Nib object loading
- Subject: Re: initWithCoder in Nib object loading
- From: Michael Watson <email@hidden>
- Date: Fri, 27 Jun 2008 08:27:47 -0400
<http://developer.apple.com/documentation/Cocoa/Conceptual/LoadingResources/CocoaNibs/chapter_3_section_3.html
>
All view objects are sent -initWithCoder:, but the "custom view"
object does something extra. After the custom view object is
unarchived, it creates your view subclass, sends the object an -
initWithFrame: message, and then swaps itself for the subclass.
--
m-s
On 27 Jun, 2008, at 07:28, John Murphy wrote:
I notice that there are a couple different init methods used for nib
loading. For instance, objects from the IB Library get an
initWithCoder message, while custom view objects get an
initWithFrame, and everything else gets an init. Why is this?
Specifically, why a special initWithCoder technique? After all,
isn't everything encoded?
_______________________________________________
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:
@bungie.org
This email sent to email@hidden
_______________________________________________
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