Re: initWithCoder in Nib object loading

Hey John - If you're thinking about overriding initWithCoder: just to do post NIB loading instantiation, I would recommend overriding awakeFromNib instead. The objects in the NIB are sent the initWithCoder: message because they're actually being decoded from an archive. Conceptually initW

Re: initWithCoder in Nib object loading

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

initWithCoder in Nib object loading

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