Re: is setFrame as optimal as setNeedsDisplayInRect?
Re: is setFrame as optimal as setNeedsDisplayInRect?
- Subject: Re: is setFrame as optimal as setNeedsDisplayInRect?
- From: Michael Ash <email@hidden>
- Date: Sat, 13 Jun 2009 03:54:39 -0400
On Fri, Jun 12, 2009 at 8:17 PM, Chunk 1978<email@hidden> wrote:
> hum... it seems that Quartz Debugger's Flash Screen function isn't
> much help with using the iPhone simulator... since it's an emulator it
> will flash the entire screen regardless if setNeedsDisplayInRect is
> called.
>
> which brings me back to my first question... i know that
> setNeedsDisplay will redraw the entire view, and by using
> setNeedsDisplayInRect will only refresh the part of the view that is
> changing, but how does setFrame factor into this? i'm assuming that
> setFrame is the same as setNeedsDisplay, since the entire view's frame
> is being set (or continuously reset with drag events), but does this
> resetting of the frame (setFrame:) affect the view's superview?
It would be helpful if you would have mentioned that you are talking
about UIView in your first message. This is primarily a Mac mailing
list and so the assumption is that you are discussing NSView.
UIViews are always implicitly layer backed. This means that each view
has a backing buffer, and superviews never need to be redrawn due to a
change in a subview.
Mike
_______________________________________________
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