On Jul 21, 2008, at 7:49 PM, Andreas Mayer wrote:
I don't know why you'd think the collection view might own the item's view. You set the view for the view item, so the hierarchy seems to be quite clear. (The collection view *might* retain the view too. That's an implementation detail.)
Well that's exactly what is important here, isn't it.
How would you get a retain cycle here? You just hold on to the collection view. Everything else should not be your responsibility.
Unless you have to have access to the collection view or the view's item controller.
If you set something, it's usually retained. Exceptions from this norm should certainly be documented - like it is with delegates.
That basically answers the original question I had, but things can get complicated and details become important.
Regards Markus -- __________________________________________ Markus Spoettl
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
