Mark Bakker wrote:
> Eric -
>
> Thanks for your reply.
> Let me give you my idea about axis('scaled') and why I am asking for a
> change (a new option would be fine as well).
OK, your explanation of the use case is very helpful. I am thinking
that the problem here is that we are trying to get the axis() function
to do too many different things--as a Matlab legacy it is already doing
quite a variety of things, and the more we load in the worse it gets.
It may be that the clean solution for your use case is to simply make a
direct pylab interface to axes.set_aspect(), because I think that this
is what really matches your use case. Doing so would be easy, and quite
consistent with the pylab interface in general. A slightly different
approach would be to make a pylab function data_aspect() that would call
gca().set_aspect() with adjustable=box (at least by default). The
reason for suggesting this is that the name "set_aspect" does not make
it clear whether we are talking about data coordinates or display
coordinates.
This may take a little more thought and fiddling, but in any case I am
pretty sure that continuing to pile things into the
bursting-at-the-seams axis() function is not a good idea.
Eric
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Matplotlib-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
