Re: Table View Blues

FROM : David Remahl
DATE : Tue Nov 19 00:23:06 2002

>>> switch the contents of the table view so often that memory
>>> allocation / deallocation is a serious bottleneck, don't you
>>> think that this would cause the table view in itself to be
>>> almost useless as an UI element?
>>
>> Absolutely not. I have several examples where it not only is necessary, but
>> works fine - given the memory stuff I can use where I have recently been.
>
> My point (usability issues ignored, for the time being), is that you can use
> what ever storage and allocation method you want. For example, you could use a
> linked list in C code, for which you are responsible of all memory management.
> The actual allocation is not a siginifiant bottle neck in most cases, but
> retain/release may be. Many else have pointed this out.
>
> In the data source, you then provide the information required by the control.
> That is seldom more than 200 cells at a time, and that happens in a quite
> short time, and is not dependant of the size of the underlying data set.
>
> / Sincerely, David Remahl
_______________________________________________
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.