Re: NSOutlineView: expanding an item retains it?
Re: NSOutlineView: expanding an item retains it?
- Subject: Re: NSOutlineView: expanding an item retains it?
- From: j o a r <email@hidden>
- Date: Mon, 24 Jan 2005 12:08:31 +0100
On 2005-01-24, at 10.57, Charlton Wilbur wrote:
I don't think retaining implies ownership strictly. Container classes
may not own the objects stored in them, after all. Retaining implies
"I have an interest in this object, and I don't want it going away
until I've made it clear that I'm done with it."
I guess it comes down to what "ownership" means. I'm not too happy
about introducing that word in this discussion, as it's ambiguous, but
I guess it's too late to change that now...
But back to the topic of this thread: Why should an NSOutlineView
retain an item provided by the data source? The data source must in my
opinion be responsible for retaining all objects that it contains for
as long as they are valid (ie. until reloadData are next called). So
what would be the point of having the outline view also retaining them?
To be able to use them after reloadData is called? Doesn't make much
sense, right?
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden