In article <[EMAIL PROTECTED]>, Sanel Zukan <[EMAIL PROTECTED]> wrote:
> > Does this mean that every widget should create an independent x drawable > > to take advantage of the compositing manager? > > It depends; mostly you will send hints to the compositing manager and > application code should not be modified at all. Some cases, like regional > translucency, requires setting appropriate visual and background alpha; > the compositing manager will handle the rest. > Theming should not be complicated either; just paint image (e.g. png) > with some alpha on widget and voila :) This will work for both cases: > > * when you want translucency with whatever-is-behind-window; CM will be > involved here Clearly, this is the simple case. > * when you want translucency with window background; CM not needed, > FLTK already have blending The current blending FLTK has is really poor, works for Fl_Image only, and does not handle correctly layered widgets with alpha at all. Remember the issue with antialiased text on labels/boxes? I was fixing the alpha issue recently, and there's nothing special about it. > Again, redrawing and/or compositing on client side is not needed. > It just have to set some stuff to make life easier for the manager. Honestly, I never investigated too much into X11's composite API, so I will stop here. > Xrender compositing can be hardware accelerated (all nv cards support > it). Since compositing mangers can use opengl as backend too, situation is > much better with the acceleration in this field. <ot> In fact, that's the principal cause of GL problems (poor performance, filled texture memory, frequent context switches), and it is the first thing I disable in all of my boxes. Not that OSX is much better. Apple tried to virtualize the VRAM for exactly these problems (quartz 3d extreme?), and miserably failed. VRAM is really precious compared to system memory. It's quite different to manage too. I look forward to see how Vista actually resolved this particular problem. (or maybe not). _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
