Hi Ben,
I suspect the designers of NSTableView decided to save themselves
having to cache values for the currently-selected row (which would
later be needed to redraw that row unhighlighted) and in doing so
doomed the rest of us to have to write such code in every single
datasource.
Hamish
On Jan 16, 2008 10:07 PM, Ben Chen <email@hidden> wrote:
Hi everyone,
I just found that when scrolling a NSTableView inside a NSScrollView
one row at a time, each time the tableview will not only ask the data
source for the new row's value but also ask for the last row's. So if
you scroll the table all the way donw, eventually it makes twice calls
as the number of rows in the table.
I been programming a app that performance of the table view is vital,
so I really want the table view call the data source as few as
possible. Does anyone know a solution?
Thanks,
Ben
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
