On Mon, Nov 9, 2009 at 3:55 PM, Andrew Straw <straw...@astraw.com> wrote: > What's the motivation of the ps backend "compositing" (rasterizing to a > single bitmap) multiple images? It seems it will, by design, preclude the > use of non-image artists between two images. I guess the motivation is to > reduce output file size. Maybe Axes.draw() should disable compositing in the > scenario where a non-image artist is sandwiched by image artists and suffer > the increased file size. >
I can't say about what the original intention was, but I guess one of the benefit is that you can have alpha compositing of multiple images. I personally think that no alpha support for images is a more serious issue than no alpha support for other artists like lines and patches. So, I'm +1 for doing the alpha compositing of images before passing it to the backends (that do not support the alpha compositing). However, as I said in my first email, I don't think there are much cases that this actually matters, while I'm also not sure about the benefit of having images above other artists like lines. Anyhow, as far as zorders between images are respected (in all backends!), it should be good. Regards, -JJ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
