On 15 Jan 2013, at 01:20, Christopher James Huff wrote: > On 2013-01-14 16:32:03 -0500, Ian MacArthur said: > >>> Is there an easy way to render a "standard" window to an image? It'd> >>> greatly streamline testing if I could do comparisons in the app itself. >> >> It's pretty easy to make a group that just renders to an offscreen >> buffer, then blit that buffer content >> onto another surface for display... I'll dig about, I think I have code >> for that somewhere... > > Turned out not to need the offscreen buffer, just read_image() was > perfect for what I was doing. I now have a test application that shows > the per-pixel difference between the OpenGL driver and whatever the > "native" driver is.
This is looking pretty cool already - I like it; though I'm not getting any time to look at it, my schedule is trashed right now. One trivial observation is that the use of FLU / flu as a namespace confused me, since there is already a (fltk-1.1) third-party add-onn lib called FLU, that I used to use quite a lot! >> Maintaining portability, particularly when we have to play well with >> the MS tools, and various embedded toolchains, means a pretty >> conservative "lowest common denominator" approach plays out best. > > Reasonable, but I find lambdas and some other C++11 features to be > major improvements that have been long overdue in C++, and particularly > useful in UI code, and any new projects I start are likely to make use > of C++11. This library uses a mixin to overlay the lambda-friendly > interface without modifications to FLTK itself. Indeed, and I have no issue with using new features in my own code, too. But for the core lib it is a problem; indeed I still support some embedded devices for which the only tool chain is based on gcc-2.95, so C++11 features are perhaps a bit beyond it! I'm sure other users are in the same situation, hence my caution about new features in the lib. Oh, now that's a thought - for the embedded targets, an EGL driver rather than a GL one, might be really neat too... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
