Re: Need help with setNeedsDisplay - Another Update
Re: Need help with setNeedsDisplay - Another Update
- Subject: Re: Need help with setNeedsDisplay - Another Update
- From: Andy Lee <email@hidden>
- Date: Sun, 11 Mar 2007 15:21:00 -0400
On Mar 11, 2007, at 2:55 PM, Yevgeniy Goldberg wrote:
I can see why there were two instances - the second instance came
from the nib.
I've deleted that instance from the nib and now I can see only one
awakeFromNib.
From the drawing perspective the problem is still there, but now
I'm dealing only with one instance of my custom view
Okay, we've narrowed the problem down.
Just as a sanity check, can you confirm that the object that gets the
awakeFromNib is the same as the object that you're sending
setNeedsDisplay: to? You can just compare the addresses printed by
the NSLog statements you added earlier.
Next, can you confirm that drawRect: is *not* being called after the
setNeedsDisplay? I know it *looks* like it isn't, but confirm this
with a breakpoint, not just by looking at the screen. You need to
rule out the possibility that drawRect: *is* being called, but maybe
it's not affecting the display for some reason, like maybe the data
values aren't what you think they are.
I see that you call setNeedsDisplay: inside a method in your view
called
updateAdsrValues:atav:dsfv:dsav:ssfv:ssav:rsfv:rsav:refv:raev:. (To
me this suggests there may be larger design issues, but never mind
those for now.) Where do you call this method?
--Andy
_______________________________________________
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