Re: NSTableView performance on Jaguar
Re: NSTableView performance on Jaguar
- Subject: Re: NSTableView performance on Jaguar
- From: Mikey <email@hidden>
- Date: Mon, 3 Nov 2003 13:24:11 -0500
I think I remember seeing some information that Panther is better about
cropping updates so that they don't force unrelated graphic elements to
be redrawn. In other words, if you change something at the top of the
window, and something at the bottom of the window, and then call the
window's [... displayIfNeeded] method:
- In Jaguar, you actually update the rectangle bounded by the two items
that were updated. This could include other things like your
NSTableView.
- In Panther, you only update the things that changed.
Perhaps this is what you're seeing. An easy way to tell would be to
run the Quartz Debug application and watch exactly how the screen
redraws are occurring.
On 3 Nov, 2003, at 10:51 AM, email@hidden wrote:
The Panther version
appears to not update unless told to (reloadData). The Jaguar version
appears to poll the source-data object every few seconds.
No, I don't think that's true. You need to reloadData in Jaguar.
The end
result is a lot more CPU use in Jaguar than in Panther. In Jaguar, the
view doesn't seem to always redraw itself properly, either. Sometimes
rows are blank, until they scroll out and back into view, or the app
is
hidden and then unhidden.
I suspect you may not be using reloadData where you should in Jaguar.
Is there something I should be aware of when using NSTableView on
Jaguar, to get the performance up and the behavior correct?
Probably reloadData.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.