• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Dirty rects getting merged together makes for inefficient drawing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dirty rects getting merged together makes for inefficient drawing


  • Subject: Re: Dirty rects getting merged together makes for inefficient drawing
  • From: Andy Lee <email@hidden>
  • Date: Mon, 19 Oct 2009 18:53:29 -0400

On Monday, October 19, 2009, at 05:58PM, "Ben Haller" <email@hidden> wrote:
>On 19-Oct-09, at 5:27 PM, Dave Keck wrote:
>
>> Would NSView's -getRectsBeingDrawn:count: help?
>
>   Well, I'm already using it in my own code where appropriate.  (Or
>actually I'm using -needsToDrawRect:).  But the problem is that a
>whole bunch of NSTableView cells are getting drawn that never got
>invalidated.  I would certainly hope that NSTableView is using one of
>these minimal-drawing mechanisms, and I assume that it is.
>
>   I think the problem is deeper (based upon what flashes under Quartz
>Debug): I think the dirty rects are actually getting consolidated such
>that NSTableView no longer has the information it needs to do minimal
>drawing.

To test this theory, might it help to use a subclass of NSTableView whose drawRect: method prints the rectangle passed to it, and see what happens when your graph views do and do not do any drawing?  And maybe the result of getRectsBeingDrawn:count: as well?

I'm curious too if you've tried Greg Guerin's suggestion.

--Andy


>  I could be mistaken about that, though, if the flashes in
>Quartz Debug show only the area that Quartz is choosing to blit over,
>and not necessarily the area that was considered dirty and redrawn.
>(i.e. if it brings over merged areas for efficiency, for some reason;
>but that seems unlikely...)
>
>Ben Haller
>Stick Software
>
>_______________________________________________
>
>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
>
>
_______________________________________________

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

  • Follow-Ups:
    • Re: Dirty rects getting merged together makes for inefficient drawing
      • From: Ben Haller <email@hidden>
References: 
 >Dirty rects getting merged together makes for inefficient drawing (From: Ben Haller <email@hidden>)
 >Re: Dirty rects getting merged together makes for inefficient drawing (From: Dave Keck <email@hidden>)
 >Re: Dirty rects getting merged together makes for inefficient drawing (From: Ben Haller <email@hidden>)

  • Prev by Date: Re: Why does my font come out looking fuzzy?
  • Next by Date: Re: Dirty rects getting merged together makes for inefficient drawing
  • Previous by thread: Re: Dirty rects getting merged together makes for inefficient drawing
  • Next by thread: Re: Dirty rects getting merged together makes for inefficient drawing
  • Index(es):
    • Date
    • Thread