Re: [matplotlib-devel] Re: Routine to show matrices?

[John H. <jdh...@ac...>]

>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:

    Fernando> OK, the perfectionist freak in me wants:

    Fernando>      ax = fig.add_axes([0.15, 0.075, 0.75, 0.8])

But using non-equal width and height for the axes seems like a logical
error that defeats the stated purpose of matshow.  Of course, in real
life this might be a hack to defeat unequal dpix and dpiy on your
monitor, but it would come back to bite you when you saved to PS,
which has the same dpi in both directions.

    Fernando> I tested this, and these values avoid problems with
    Fernando> labels running into walls or too much whitespace for
    Fernando> extreme aspect ratios.  For more square ones, the change
    Fernando> is barely noticeable.  You'd make me infinitely happy if
    Fernando> you indulged this little nit :)

Hmm, you solve my problem on ipython-users and I'll solve yours.  :-)

Actually, I looked a bit at it yesterday and could replicate it.  I
haven't figured out where the root evil is.  Is it known to be safe to
run two separate tk processes in python?  Eg, I'm not 100% convinced
its a matplotlib bug, but may be 


JDH