On 21.02.2010, at 18:58, G Thompson wrote: > On 02/21/2010 12:34 PM, Albrecht Schlosser wrote: >> This is known behavior and can't be changed for FLTK 1.1. >> >> FLTK 1.3 works w/o problems with your patch. If you really need so >> many children, you should consider using FLTK 1.3. The drawback is >> that FLTK 1.3 is still under development (beta state), and that it >> is using UTF-8 internally. If that's okay for you, then you should >> give FLTK 1.3 a try. It's almost API compatible with FLTK 1.1. Most >> programs work without any changes. >> >> Albrecht > > Really? I'm using fltk-1.3.x-r7063 > > It's not about having "so many" as it is just a few large items (hence > the reason for the scroll pane in the first place).
In FLTK 1.1, we used 16 bits for graphics coordinates. In 1.3, we use 32 bits. However, if the underlying OS uses 16 bit, the rendering will still be messed up. We have that as an issue on our bug list, but have not gotten around to fix it yet. But generally, a scroll with more than 16000 pixels is hard to maneuver for the user. Maybe a different set of widgets is a better solution? - Matthias _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
