Hi Alan
I think I agree that removing agg and freetype is probably a good plan, so that
drops us down to 2 backends. I had just written a whole email about why we need
to support wxDC and wxGraphics context because wxGraphicsContext give
antialiased rendering with alpha support and wxDC gives non-anit-aliased
hardware accelerated rendering and access to other device and file DCs, my
final sentence was going to be - "I don't know why wxGraphicsContext is not
impimented with inheritance from wxDC". Then I thought I'd google to find out
why and it turns out that there is a wxGCDC which does exactly that. However on
my 2.8.11 version of wxWidgets wxGCDC isn't mentioned in the docs and it isn't
included in my build, but it appears that the source includes the requird
files. Perhaps there is a configure flag to turn it on and/or perhaps it is not
fully supported in 2.8. I will investigate further. If wxGCDC does work fine
then I think we can do away with
wxGraphicsContext too, but I think this will need some testing first - in
particular there is a statement somewhere in the docs saying wxDC does not
generally support alpha giving a single exception which is for a Mac OS
context. I'm not sure if wxGCDC will support alpha like wxGraphicsContext does.
If that all works as expected then a single backend for wxWidgets sounds ideal.
It would significantly cut the required code we need to maintain.
Phil
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel
