On 22.09.2009, at 18:44, andrei_c wrote: (...) > Since most people posting on this forum are the actuall FLTK > developers, you know exactly what you have planned for future > versions of FLTK, like if you're going to make the drawing functions > to draw on an array of floats or doubles too, not just of uchars, etc. > So cosidering all my needs(especially 48 bit color) and all the > problems I've encounteres and what you FLTK developers have planned > for future versions of FLTK, what would you recommend me to do??To > just use offcreen drawing as it is implemented in a future version > of FLTK( I can wait I guess) or to make my own, like a function that > draws a line or a circle, etc. ???
Ian gave a perfect list of reasons and targets for FLTK. Interestingly, FLTK was originally written by Bill Spitzak to keep Nuke going, a 2D compositing software, which renders images in true floating point space (32 bit per color component, 128 bit for RGBA). It is important to see that GUI rendering needs not even 24 bits to be usable and quick. It makes little sense to create a Button in a 128 bit screen buffer. This is why FLTK sticks with whatever the standard graphics cards can display, which is currently 24 bits. Nuke solved the problem very elegantly (and extremely fast) by using OpenGL to render whatever was in the 128 bit buffer onto the screen. Fast, light, and just what the users needed. Matthias _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
