Re: Value of self changes
Re: Value of self changes
- Subject: Re: Value of self changes
- From: Quincey Morris <email@hidden>
- Date: Fri, 15 Nov 2013 00:01:36 -0800
On Nov 14, 2013, at 23:41 , Jerry Krinock <email@hidden> wrote:
> this cell would receive -drawWithFrame:inView:, but the value of self is *different* than the original value of self, which I'd stored in an instance variable during the -init of this instance.
> Can anyone suggest how ’self’ could be changed?
Except that this doesn’t sound like a description of self “changing”. It’s not “this” cell receiving -drawWithFrame:inView:, but a different one — as evidenced by a different value of self, surely?
Your coping strategy sounds good. You only mess with your static variable when dealing with the original cell, and you allow the others to be transient. Is there anything to care about in that? Incidentally, there’s no prima facie reason why this should cause the extra cells to leak.
> I realize this is probably a good lesson in Why It’s a Bad Idea to Use Non-Standard Controls, and if I spend too much more time on this, I’ll probably rip it out and put in more conventional column-attribute controls, probably a checkbox or a checkmark on/off menu item for each attribute.
TBH, I’d suggest you simply move on, and change your table over to be view-based, which should enable you to keep both the popup menu header and your sanity. Why waste effort on dead NSCell technology?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden