Re: [matplotlib-devel] Buglets in svg backend?

[Fernando P. <fpe...@gm...>]

On Thu, Oct 14, 2010 at 8:15 AM, Michael Droettboom <md...@st...> wrote:
> I'm not sure what's causing this.  I don't have a Python >= 2.6
> environment with all the Qt bells and whistles to test ipython HEAD with
> (our house standard here is still 2.5)...  Once I find the time for
> that, hopefully I can see what's going on.  But I suspect "paste()" is
> doing something fishy here.  Saving an SVG from the standard matplotlib
> window does not cause the "dpi changing without the window size
> changing" problem shown here.  I would suggest looking at the code
> triggered from the save dialog in matplotlib and compare it to what
> "paste()" is doing.

Here's how to reproduce it in plain python/ipyhon:

from cStringIO import StringIO
plot(rand(100))
canvas = gcf().canvas
string_io = StringIO()
canvas.print_svg(string_io)

Now try panning the figure.  Once you pan it and it redraws, the
problem shows up.

This is not seen via a savefig() call, but calling directly print_svg
seems to be the issue.  Are we not supposed to use print_svg
ourselves?  Should we only use savefig()?

Cheers,

f