I have committed another revision of the aspect-ratio handling. It seems to work pretty well, and I think pan/zoom work in a reasonable fashion now. Many times in the past, however, I have thought that aspect-ratio handling was working adequately, and every time someone has found a major bug. This time is probably no exception.
There can be some anomalies when the window is resized quickly--that is, grabbing a window corner and slinging it around with axis('equal') can cause some incorrect choices of the view limits. I haven't figured out why. Although I certainly would like to understand and fix it, it is not a top priority at the moment because I don't think it is a major problem in practice.
----- Original Message -----
From: Andrew Straw <strawman@...>
Date: Saturday, May 27, 2006 12:07 pm
Subject: Re: [Matplotlib-users] autoscale and "equal aspect" mode
To: Eric Firing <efiring@...>, matplotlib-users@...
> I'm having trouble with axis('equal') myself -- I'm happy to take a
> lookin the source, but maybe it's a simple and easy bug. The issue I'm
> having is readily apparent with examples/axis_equal_demo.py --
> using the
> pan/zoom mode and holding the right-mouse button down to zoom, I
> noticeseveral issues:
> 1) moving left-and-right seems to affect the position, not the zoom
> level2) moving up seems to zoom in (as expected)
> 3) moving down zooms out as expected, but past a certain point,
> only the
> vertical axis gets re-scaled and breaking the equal-aspect.
> Eric Firing wrote:
> > Mike,
> > I thought all the aspect handling was finally working correctly. If
> > you generate a simple example, I will take a look. The simpler the
> > better, of course. I presume you are working with a recent svn
> > Eric
> > Michael P. Mossey wrote:
> >> I'm using this aspect mode:
> >> axes.set_aspect( 'equal', adjustable='datalim' )
> >> With several xy line plots on the axes, autoscaling doesn't seem to
> >> occur properly. It cuts off part of the data. Is this a known
> issue?>> I don't have a simple script to replicate it---I'll have
> to pull that
> >> out of a larger program---but just wanted to check if it is
> known. I
> >> don't see anything in the bug tracker.
> >> Mike