Skip navigation.
 
mlRe: NSTableView limitations?
FROM : Alexey Zakhlestine
DATE : Wed Dec 22 21:09:44 2004

David Christensen wrote:
> Alexey,
>
> I have had a circumstance where the scrolling view runs into problems
> with huge data views -- turns out it was a problem with the float
> representing the coordinates running out of precision.
>
> I don't know off-hand at what point the float loses its precisions, but
> I assume it is the maximal value of the mantissa (23 bits, as google
> just informed me...).
>
> That would mean that 8388608 would be the highest integer addressable in
> this case, so if your table allocated 20 pixels per row you would be
> limited to 419430.4 rows without visual distortion.
>
> You may be able to get NSScroller to treat its coordinates as doubles or
> integers, in which case you could have a view into a partition of the
> total set, but  I pretty much moved on to something else and never got
> it working.


thanks, David.. it describes.

yep.. such limit seems to be a safe bet.. but it's not enough for my
purposes :-/
I guess, in the end I will be creating my own control..

Related mailsAuthorDate
mlNSTableView limitations? Alexey Zakhlestine Dec 22, 20:12
mlRe: NSTableView limitations? Scott Stevenson Dec 22, 20:22
mlRe: NSTableView limitations? Alexey Zakhlestine Dec 22, 20:36
mlRe: NSTableView limitations? David Christensen Dec 22, 20:36
mlRe: NSTableView limitations? Alexey Zakhlestine Dec 22, 21:09
mlRe: NSTableView limitations? Alexey Zakhlestine Dec 22, 22:14
mlRe: NSTableView limitations? Markus Hitter Dec 23, 00:21
mlRe: NSTableView limitations? Timothy J.Wood Dec 23, 02:24