Re: Updating NSTableView
Re: Updating NSTableView
- Subject: Re: Updating NSTableView
- From: Corbin Dunn <email@hidden>
- Date: Thu, 14 May 2009 08:14:05 -0700
On May 14, 2009, at 7:49 AM, I. Savant wrote:
On Thu, May 14, 2009 at 10:41 AM, Scott Ribe <email@hidden
> wrote:
First a fast way to read the data off disk to begin with, for start
up time.
Then caching of row heights when they are calculated. Finally
binary search
of row heights/positions when mapping coordinates to row indexes.
Of course depending on what calculations are truly necessary, the
first draw
may still be slow, but there's really no reason a redraw should be
slow
after changing one (or a few) values.
Informative, thank you.
Yup, Scott's idea sounds like a good plan. Most people get good
performance out of variable row heights by doing some sort of caching
or heuristic that quickly determines the row height.
-corbin
_______________________________________________
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