> imm wrote: > > On 10 May 2008, at 2:03, Greg Ercolano wrote: > >> My only guess is that you might be reaching a 16 bit integer limit, > >> since I believe in FLTK there's a +/-32767 limit on x/y positions, > >> and 32767/1600 is around 20, which is about the height in pixels > >> of a standard font, including descenders. > > > > Note that, technically, the +/-32767 limit is driven by constraints > > of the underlying win32 and X rendering systems. > > Both fltk-1.3 and fltk-2 attempt to work around that limit, so if > > that *is* the problem, the OP may get different (hopefully better!) > > results using fltk-1.3. > > > > That said, for very big tables, I'd tend to try and store the data > > internally in some sort of structure, and only render the current > > visible screenful into the actual table. > > This is obviously more work for the programmer, but results in a > > "table" that can be as big as you have memory to hold, not limited by > > system architectural issues. > > Yes, as this is what e.g. Fl_Table does. > > I know I can set the Fl_Table 'testtablerow' demo to create > two 10,000 x 10,000 row/col tables, and it still runs normally > and scrolls quickly. > > But I don't think that's what the OP is using. >
Thanks guys. I think you have guessed the problem correctly. I don't understand the workaround correctly at this moment, but I will try something. I am using fltk 1.1.7 currently. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk

