Re: Proper Way to "Unload" a Loaded Nib w/Bindings [Solved, Maybe]
Re: Proper Way to "Unload" a Loaded Nib w/Bindings [Solved, Maybe]
- Subject: Re: Proper Way to "Unload" a Loaded Nib w/Bindings [Solved, Maybe]
- From: James Bucanek <email@hidden>
- Date: Tue, 27 Mar 2007 21:35:00 -0700
Keary Suska wrote on Tuesday, March 27, 2007:
>I should have been more specific--I was referring to the Resource
>Programming Guide, which states:
>
>"After releasing the top-level objects, it is a good idea to clear any
>outlets pointing to objects in the nib file by setting them to nil. You
>should clear outlets associated with all of the nib file’s objects, not just
>the top-level objects."
As I explained, that makes sense for any connections that are weak (i.e. non-retained) references, as any of the objects referenced might have been released. But again, that's not a nib issue it's a retain issue. It just show up in connections because simple connections are, by default, not retained.
>My first assumption was that it meant in-nib outlets, but a closer reading
>could indicate that they mean programmatically-created outlets to nib
>objects from outside of the nib itself. I assume this is possible, though I
>have never done it or read about it.
It applies to any references, nib-created or otherwise. The retain/release rules are simply and apply equally to nibs as programmatic connecctions/references.
>Since I don't seem to be having any problems, perhaps I shouldn't worry
>about it.
Works for me. ;)
--
James Bucanek
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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