Re: Should objects returned by indirection be autoreleased
Re: Should objects returned by indirection be autoreleased
- Subject: Re: Should objects returned by indirection be autoreleased
- From: Bill Bumgarner <email@hidden>
- Date: Sat, 13 May 2006 13:12:14 -0700
On May 13, 2006, at 12:57 PM, Eric wrote:
Now comes another question that Bill brought up, of whether it's
appropriate to use representedObject for my purpose. What I have
is a NSCell that represents a bookmark button. I'm using the
representedObject to refer to the actual bookmark model object it
represent. Does this warrant the use of representedObject?
That definitely sounds like an appropriate / correct usage pattern
with the caveat that a client of your cell that expects to also be
able to set the represented object will stomp on our bookmark. As
long as you are the only user of your Cell class, you'll just have to
keep that in mind. :-)
Also, keep in mind that tables, matrices, and outline views do not
generally have a cell per column/roll position. There is typically a
prototype cell that is used to "stamp" contents into each spot that
has data to be displayed.
b.bum
_______________________________________________
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