Re: NSTableView bug?
Re: NSTableView bug?
- Subject: Re: NSTableView bug?
- From: Shawn Erickson <email@hidden>
- Date: Thu, 2 Jul 2009 09:36:20 -0700
On Thu, Jul 2, 2009 at 8:37 AM, Michael Ash<email@hidden> wrote:
> On Thu, Jul 2, 2009 at 10:51 AM, Chris Carson<email@hidden> wrote:
>>
>> Hello,
>>
>> I've created a simple application with an NSTableView. I have written a delegate for this table, numberOfRowsInTableView:objectValueForTableColumn:row:, that returns the number of rows in the table when requested.
>>
>> My application uses the table view to display hexadecimal data on a flash memory chip, with 16 bytes displayed per row. As a test, I tried returning a large number for the number of rows, 0x1000000. When I scroll through the table, everything looks okay for the first 14 million rows or so, after which the gray horizonal cell separator disappears and the row data begins to shift by a pixel per row, until it eventually is superimposed on the row above it. This seems like a bug with the NSTableView class, but perhaps I'm doing something wrong. Has anyone else run into this problem?
>
> Known problem:
>
> http://www.google.com/search?client=safari&rls=en-us&q=nstableview+14+million&ie=UTF-8&oe=UTF-8
>
> Either restrict your app to running in 64-bit mode (which will cause
> the graphics system to use doubles instead of floats) or write a
> custom control.
...or seriously reconsider the utility (expectation) of having
millions of row in a table view.
Do users really want to scroll thru that many rows? Can users work
with that much data? etc.
In other words will this really be a problem without first causing
usability problems for your users.
-Shawn
_______________________________________________
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