On 6 Feb 2009, at 19:52, Roman Kantor wrote: > I am late to this discussion and did not follow it (so forget my > ignorance), but why the offscreen drawing needs to be within draw > (so it > is called during Fl::flush()) and not the other way around? I thought > that you can draw to the ofscreen at any time.
Sure, that can work too - the OP was wanting to capture (to an image, or a printer or etc.) a large widget hierarchy built up as a child of an existing Fl_Group, so my "solution" was to provide a mechanism to render an offscreen for that enclosing Fl_Group. In that way it (the derived Fl_Group substitute) can be simply dropped into the existing application to get the desired effect. That said, I actually think it is a fairly good way to handle the offscreen anyway, and have done it that way for a number of applications. But the offscreen does have other advantages - you can do incremental drawing to an offscreen more easily, and it can be accessed outside the normal draw hierarchy if you wish/need to. -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
