On 17 Mar 2012, at 20:51, J. Liles wrote:

> So, I believe my only remaining problem is one with clipping. I'm
> getting a poor interaction where child windows like Fl_Menu_Window end
> up clearing large portioins of the main window. I'm not sure what do
> to about it though without involving a lot of extra work (and I feel
> like I've wasted enough time on this already). FLTK's Xlib graphics
> driver uses the Xlib Region stuff to compute the clipping region, but
> there's no way that I can find to get the dimensions back out of a
> Region--which is extremely frustrating.

Yup - tricky...
Still, it's pretty cool what you did achieve - be a shame to lose that work...

> I'm also a bit frustrated because I ran across some posts by Bill
> Spitzak on the Cairo ML which intimated that he as already implemented
> pure-Cairo rendering in FLTK--but apparently didn't feel like sharing
> it with the rest of us. Boo.


When was this? I seem to recall Bill was looking at Cairo rendering for some of 
the fltk-2 experiments, but that must be many years ago now. I can't imagine 
he's looked at that recently though.
If he did anything, it'll be in the fltk-2 svn, for what it's worth, though 
porting that into fltk-1.3 (or indeed fltk3) would be far from painless.

> Anyway, I'm beginning to think that there's not really an advantage to
> be had from pure Cairo rendering on the xlib backend--due to the mixed
> performance and this clipping issue. I think in Non* I'll just use
> Cairo directly for the things I need it for (maybe adding a set of
> direct cairo box types too--because FL_ROUNDED_BOX etc look like crap
> without antialiasing) and use the basic FLTK drawing for everything
> else.  It still may be valuable insofar as the possibility of
> rendering FLTK using cairo's GL and other backends, though.

Yup - we ended up with a mix of fltk and GL; something like that may work for 
you, too?
Though at the time Cairo was much less mature, so maybe fltk + Cairo is the 
best choice now?





_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to