a hunch that it was due to some interaction
between fixed-72-dpi code, rounding the number of pixels, and
subsequent rescaling. However, the image scale still seems to be off
even when the dpi setting is a multiple of 72.
Mike
On Aug 6, 2009, at 10:42 AM, Michael Fitzgerald wrote:
>
>
I've added this to the sourceforge bug tracker, ID 2832896.
Mike
On Aug 5, 2009, at 3:32 PM, Michael Fitzgerald wrote:
>
> Hi all,
>
> I've come across an apparent bug in imshow when outputting to PDF
> and EPS files. (I haven't tested other vector formats.
Hi all,
I've come across an apparent bug in imshow when outputting to PDF and
EPS files. (I haven't tested other vector formats.) It manifests as
a small scaling error between the raster image and the axes coordinates.
I have attached a test script to illustrate the problem. The
(corr
Hi all,
I found a small bug in LineCollection, which gives an exception when setting
alpha. This is manifested in e.g. hlines and vlines:
In [1]: hlines((0,),(-1,),(1,),color='b',alpha=0.1)
---
IndexError
Hi all,
I encountered problems with the Arrow patch, which broke sometime
recently. I'm attaching a fix (diff against svn r4999).
Best,
Mike
arrow_patch.diff
Description: Binary data
-
This SF.net email is sponsored
Hi all,
I found a small bug, where Figure.clf() was erroneously leaving some axes
instances in the Figure.axes list. It turns out the method was deleting
items from the list while iterating over it. Attached is a patch.
Mike
Index: figure.py
=
Hi all,
I have a question about the PS backend (building on the thread
"imshow with PS backend" from ~ a month ago). Evidently this backend
is fixed at 72 dpi. This isn't a problem with vector information.
However, it would seem that one would want to use a higher resolution
when plott
