On 04.03.2011 17:22, Greg Ercolano wrote: > However, it depends how many widgets you stick into each item; > if each item had a few buttons and an Fl_Input, then it might > be a bit slower, I didn't check.. but I think it would scale > fairly well. > > There is some limit imposed by the size of signed shorts > which used to come into play due to pixel sizes wrapping > around at about 32768, but I /think/ in 1.3.x that was > extended to the size of signed ints.
Yes, it is, and AFAIK it works flawlessly on Windows and Mac OS, but there are still a few restrictions when using X11 with its 16-bit coordinate system. All box, line, and background drawing functions work well (are clipped internally), but other drawing functions (e.g. circles) and maybe coordinate transformations can't be used on huge widgets on X11. This means that you can use a huge Fl_Scroll [1] with a solid background, but if you try to draw some objects on the Fl_Scroll's background itself, you *must* do the clipping in your (derived) draw() method, otherwise the results are undefined. However, drawing many single widgets in a huge Fl_Scroll works well, since the widgets are clipped correctly. Albrecht [1] huge means that the Fl_Scroll itself is visible in the usual window, but the child widgets' area extends over more than +/- 32768 pixels horizontally and/or vertically. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
