Re: Table View Blues (summary)

FROM : j o a r
DATE : Wed Nov 20 11:04:03 2002

On Tuesday, Nov 19, 2002, at 15:44 Europe/Stockholm,
<<email_removed>> wrote:

> A file of several hundred KB should load and reload instantaneously.
> Now if the table view can just shrug its shoulders and say "he says
> there are no rows, OK, so there's no rows" - if it's that simple, then
> we're over one hurdle.

I think it's that simple with regards to NSTableView as a view
component. It only checks to see what rows to draw, asks the delegate
for the cell contents and draws.

> But underneath - in the data management - something more streamlined
> has to be engineered. Just guessing, but is there a way to work all
> this into an autorelease pool? For that would solve it all - given
> that the pool doesn't waste valuable real time...

How do the code that you've benchmarked deal with this? Looking at some
snippets of that code might give us some clues to where to optimize. In
that code, what is the most significant bottle neck that you've
identified?

j o a r
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.