> Any objections to changing the browser.cxx demo to use > Fl_Double_Window > instead of Fl_Window? > > Maybe all demos should use Fl_Double_Window's (except the demos that > demo single buffering, if any) > > Makes a big difference in 'flicker' on my linux box, > and I can see where flicker is something that might put people off.. > I think someone on fltk.general wasn't sure what caused the flicker > and thought it was inherent to FLTK, not realizing it was just a > matter of using double buffered windows instead..
I'd vote yes to this, but with some caveats... - It used to be the case (with fltk-1.1) on some platforms that *if* you parented a FL_GL_Window inside a FL_Double_Window you *sometimes* got issues with the GL window apparently not refreshing, and showing up black when the app launched, and so on, generally being a bit odd. I think there even used to be a STR about this, although I can't quite find it now... Anyway, I do think we should make double-buffering the default for the demos, to make them as "nice" as possible, but we need to check that we don't break GL windows in the process. - As stated above, where we *want* to show single-window buffering, we need to not change. - A growing number of platforms (well OSX and Vista anyway, possibly others with compositing WM's or etc.) are inherently double buffered, so if we *also* double-buffer the windows on those hosts, that's probably redundant. But I can't see how we could efficiently determine, at runtime, whether to double-buffer or not... -- Ian 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
