Hello,
I see a significant difference in plots generated with two recent
versions of matplotlib, and unfortunately not in favour of the newer
one, otherwise there would be no reason to write here, I guess.
The problem is following, I plot some data wich might be undefined in
some cases. For ex
Sorry about that. This bug has now been fixed in SVN r6661. It will
make it into the next maintenance release.
Mike
Andres Luhamaa wrote:
> Hello,
>
> I see a significant difference in plots generated with two recent
> versions of matplotlib, and unfortunately not in favour of the newer
> on
First, *thank you* to whoever did the Mac OS X backend. It's much
faster and smoother, and seems to behave much more reasonably all
around. As in, show() actually does what it says it's supposed to do,
and the figures don't have to be re-sized to draw themselves!
However, there seems to b
Can someone explain to me how/why the figure normalized [0,1] coordinates
depends on the figsize property? At least this is what it looks like to me.
This affects axes placement and so far I haven't been able to do what I
want.
I want to have square plots placed without spacing between them and w
ramirodsl wrote:
> Can someone explain to me how/why the figure normalized [0,1] coordinates
> depends on the figsize property? At least this is what it looks like to me.
> This affects axes placement and so far I haven't been able to do what I
> want.
>
> I want to have square plots placed withou
Dear all,
I'm using matplotlib together with ipython --pylab and have a plot
open and can select/deselect points there with the picker and they
toggle between o and x. When I do that my matplotlib running under
Leopard 10.5.6 and MacOSX backend raises an exception:
--
