> I know this example is just to illustrate the question our > friend had( to understand the use of offscreen methods), but > I was wondering if I wanted to do exactly the same example > you did, if I just create the main screen as Fl_Double_Window > as you did would solve all the double buffering problems, and > I wouldn't need to care about making a offscreen draw method, > because the son object would draw in the main screen's draw > method which is a offscreen draw. Am I right or do I need to > have all my objects in the screen doing double buffering even > if my parent window is already Fl_Double_Window?
I am not sure I understand the question, but if your outer window is a double window, that should take care of the buffering for all its child widgets, so they should not flicker. The only advantage of the off-screen in that case might be that you can use it for incremental drawing, which you can not easily do with regular fltk rendering, but probably would not want or need in general. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
