Fabien Costantini wrote: > Ok, I finally vote a +1 on Mike's proposal > in order to make now a clear decision is made on that point > (mike's approach vote majority) > and also because thinking about it twice : > i think it's the simplest (yet powerful) approach > to generic surface handling permitting > not to change too much existing widget architecture > (like the underlying & complex symbol architecture) > and so we can expect not a lot of regression as well > which is an important point too ... > > As A first increment, I propose to implement the > Surface > -- Offscreen > > part of the architecture as we need that one urgently > > and so that we can *Finally* remove Image::make_current as it was planned.
Great! Might as well implement this on your fctrunk branch as part of the fixups, so that we have a complete changeover that can be used. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Internet Printing and Document Software http://www.easysw.com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
