Yes, I made the changes into 2.0. I thought that FLTK1.x didn't support Cairo so I thought it'd be obvious from context.
I made wrapper function for clip_region that accepts X Region as parameter (as well as cairo_rectangle_list_t) if cairo is being used to allow the old code in Window/CreatedWindow to interact with clipping system. Not sure if the code would still work on Win32 or OSX though. > Is this in the 2.0 code? > > I was looking at this as well. My plan was to pretty much ignore X > clipping regions. If the window gets an expose, it figures the entire > window is damaged. > > Jasper Mattsson wrote: > > Hi, > > > > Cairo experimental backend does not currently support clipping properly. > > Today I made a quick hack to make it work, except for the clipout function. > > > > I am interested in making a patch for FLTK to make the clipping work. > > > > However, there are (at least) two approaches to implement this: > > > > 1. Rename Region to Region_type or something everywhere and use > > platform-specific typedefs, eg. typedef cairo_rectangle_list_t* Region for > > Cairo. Simple typedef cairo_rectangle_list_t * Region or #define won't do, > > since Region is already declared in X headers. > > > > This approach has the following problems: X Regions are still used in some > > other code, eg. Window and CreatedWindow. Also, changes to headers (x11.h) > > would have to be made. > > > > 2. Convert X region objects to cairo_rectangle_list_t. This will of course > > not work on other platforms than Linux, a different approach would have to > > be taken for these platforms. > > > > In the quick hack I've made, I went with the renaming. If I am to make a > > patch, which approach would you prefer? Or do you have any other ideas for > > the implementation? > > > > - Jasper Mattsson _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
