Re: [fltk.development] Doublebuffering issues andgeneralthoughtsfrom a frustrated long time FLTK user.

2012-04-04 Thread Matthias Melcher
It should be possible to have a coding style flag in each widget that - among other things - makes a widget window or group relative. The code is all there already because OS X has no convept of subwindows and implements group-relative coordinates in FLT 1 already. __

Re: [fltk.development] Old FLTK2/Cairo poll Was: Re: Doublebuffering issues and general thoughtsfrom a frustrated long time FLTK user.

2012-04-04 Thread MacArthur, Ian (SELEX GALILEO, UK)
> Cairo support on 1 was quite limited. On 2 it was better, but never > complete IIRC. Sinc 1.3/3.0 we have a driver system for rendering which > means that any frontend can be added to FLTK in a somewhat ordeely > fashion. I suggest to add Cairo support as an optional library. This > allows for t

Re: [fltk.development] Doublebuffering issues and general thoughtsfroma frustrated long time FLTK user.

2012-04-04 Thread Matthias Melcher
I agree with pretty much evrything in this mail except one: please do not drop x11 support. Pango and Cairo are just not an option for embedded developers. Maybe rendering into RAM and then just copying over the block is best. At least as some minimal driver for any platform. ___

Re: [fltk.development] Old FLTK2/Cairo poll Was: Re: Doublebuffering issues and general thoughtsfrom a frustrated long time FLTK user.

2012-04-04 Thread Matthias Melcher
Cairo support on 1 was quite limited. On 2 it was better, but never complete IIRC. Sinc 1.3/3.0 we have a driver system for rendering which means that any frontend can be added to FLTK in a somewhat ordeely fashion. I suggest to add Cairo support as an optional library. This allows for the end u