I wrote myself a little program which juggled five commands in all possible
orders saving each plottingresult in a png. What I could see was that (with
autoscale_on=False) the commands
had to obey two rules. Then and only then the plot looked like I wanted
(i.e. it had the correct limits given by axis([...]) and a circle looked
like a circle).
(i) plot() has to be before axis([-2,2,-3,3])
(ii) imshow() has to be before axis([-2,2,-3,3])
I think (i) everyone knows from everyday experience with MPL. Then (ii)
doesn't suprise too much.
I put axis('equal') AND axis('scaled') in, just to check out
if everything works fine. It seems to me that axis('scaled') overrules
In other words: I suppose axis('equal') doesn' set fixLimits=False.
I - preferring axis('scaled') - doesn't find this to bad. But nevertheless
it could be confusing to the user who prefers the other option ... on the
other hand: Propably no-one uses axis('equal') AND axis('scaled') in one
program (except me doing a 120 permutations
Still: I can't become a really friend of this. If autoscale_on=True I would
understand (i) and (ii). But it is False. When plotting doesn't autoscale
why are the limits changed? In other words: Why (i) and (ii)? You could
propably say: We already talked about the difference in
But this is not true for axis('scaled'). Here the order doesn't play a role
(At least I saw this in a seperate example and I also couldn't figure out
that the order played a role for 'scaled' in my permutations - notice the
"Then and only then" before (i) and (ii)!)
That's as far as I came right now.
PS: I don't know if this permutation-doing program is of any use to you.
That's why I haven't attached it. If you would like to have it - let me know
... but I wouldn't exhibit it in the Louvre if you know what I mean
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner