Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Is setNeedsDisplayInRect: smarter than I thought?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is setNeedsDisplayInRect: smarter than I thought?

Subject: Re: Is setNeedsDisplayInRect: smarter than I thought?
From: "Shawn Erickson" <email@hidden>
Date: Tue, 9 May 2006 15:56:17 -0700

On 5/9/06, Eric <email@hidden> wrote:

Could someone help me clear up the concept?


Yup it clips based on the set of invalidated rects. Cocoa (and Quartz)
could in some situations optimize out drawing based based on the
invalidated rects/clipping and of course it can optimize out
blitting/copying/compositing/etc. things outside of the clipped
region.

Have you reviewed the following?

<http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaViewsGuide/Optimizing/chapter_7_section_1.html>

..and..

<http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaDrawingGuide/index.html>

-Shawn
_______________________________________________
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



References:  
  >Is setNeedsDisplayInRect: smarter than I thought? (From: Eric <email@hidden>)




Prev by Date:
Re: Quit menu item undimming itself?!

Next by Date:
shared instance and nstableview

Previous by thread:
Is setNeedsDisplayInRect: smarter than I thought?

Next by thread:
Does a NSView's bounds.size always equal to frame.size?

Index(es):

Date
Thread