Hello,
If I use autoscale_view than:
* plt.text appears outside x and y coordinates
* and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
and ax.set_ylim(0)
What did I wrong?
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
I just remembered that there has been a bug in old version of
matplotlib that annotation_clip parameter is not correctly set when
given as a keyword parameter of "annotate" function. The bug has been
fixed.
http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/msg15068.html
As a work
On 8/28/10 3:59 PM, Stan Schymanski wrote:
> Hi JJ,
>
> Thanks for the advice. However, the annotation_clip=False addition does
> not make a difference to me. I am using Matplotlib from within Sage,
> though; not sure if this makes it behave differently.
>
FYI, matplotlib in Sage is still at matp
Hi JJ,
Thanks for the advice. However, the annotation_clip=False addition does
not make a difference to me. I am using Matplotlib from within Sage,
though; not sure if this makes it behave differently.
Cheers
Stan
On 8/28/10 5:09 PM, Jae-Joon Lee wrote:
> I think this change has been there for
Thanks for reporting.
It turns out a (major) bug in gridspec, which should be fixed in r8667 & r8668.
You code should work (except the rowspan and colspan needs to be
exchanged for ax3 and ax4).
Regards,
-JJ
On Sat, Aug 28, 2010 at 2:17 PM, Erik Tollerud wrote:
> If been playing around with t
I think this change has been there for a while.
For recent versions of matplotlib, the default behavior of annotate is
that, when xycoords=="data", the arrow is drawn only when the
annotated point is inside the axes.
To override this behavior, use annotation_clip keyword parameter.
pylab.annotate
On 8/27/2010 10:13 PM, Adam Gustafson wrote:
> I found a web page in which someone has done the horrible task of
> figuring out how the hell you compile in Cygwin. Details below:
>
> http://innuendopoly.org/arch/matplotlib-cygwin
>
> In short, the Cygwin compile runs into TONS of errors as is, a
On 08/27/2010 05:17 PM, Chiara Caronna wrote:
> Ok, it is a backend issue:
> I checked and I was using Qt4Agg
> as soon as I changed to TkAgg the script worked fine...
> still is this normal or is it a bug?
> thanks for your suggestion and help!
Chiara,
As a workaround for Qt4Agg, you can follow
