matplotlib-users Mailing List for matplotlib

.draw()

On Sun, Oct 30, 2011 at 10:51 AM, Daniel Welling <dan...@gm...> wrote:
> Greetings, MatPlotLibbers.
>
> Since 1.1, pyplot.draw() in interactive mode only updates the current axis.
>  If I want to update many axes, I need to use sca() and draw() for each one.
>  Is there a way to update all axes?

I'm not seeing this, and I'm not sure *why* it would be occurring for
you.  plt.draw triggers a call to fig.canvas.draw which calls draw on
all axes.  Here is some example code in ipython, which has 'ion".

  In [2]: fig, axes = plt.subplots(2)

  In [3]: axes[0].plot([1,2,3])
  Out[3]: [<matplotlib.lines.Line2D at 0x4b90550>]

  In [4]: axes[1].plot([1,2,3])
  Out[4]: [<matplotlib.lines.Line2D at 0x4b90610>]

  In [5]: plt.draw()


The call to 'plt.draw' on line 5 triggers a draw to both axes.  Can
you provide an example which exposes your problem?  Please also
provide backend and OS information

  In [6]: !uname -a
  Linux pinchiepie 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25
UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

  In [7]: import matplotlib; print matplotlib.__version__
  1.2.x

  In [8]: matplotlib.rcParams['backend']
  Out[8]: 'WXAgg'


JDH

Greetings, MatPlotLibbers.

Since 1.1, pyplot.draw() in interactive mode only updates the current axis.
 If I want to update many axes, I need to use sca() and draw() for each
one.  Is there a way to update all axes?

Thanks.
-dw

	I encountered a strange error when trying to put some annotations on 
a graph.  I was able to simplify it to this:

pyplot.plot([1, 2, 3, 4], [0, -1, -2, 8])
pyplot.annotate("Blah", xy=(2, 2), xytext=(-20,-20), 
textcoords='offset points',
                 bbox=dict(boxstyle='round,pad=0.5'),
                 arrowprops=dict(arrowstyle='fancy', 
connectionstyle='arc3,rad=0'))

On my system (matplotlib 1.1.0 with Python 2.6 on Windows XP), this 
causes a long traceback culminating in

File "C:\Program Files\Python\lib\site-packages\matplotlib\bezier.py", 
line 129, in find_bezier_t_intersecting_with_closedpath
     raise ValueError("the segment does not seemed to intersect with 
the path")

	Increasing the xytext coordinates (in absolute value), to for 
instance (-50, -50) works with no error, and it also works without the 
special bbox style.  Just guessing from the error message, it looks 
like certain combinations of fancy patches are causing problems 
because the shapes don't intersect in the way the drawing code assumes 
they should.

	I don't see anything in the docs about such edge cases, so this looks 
like a bug.  Judging from the way that small tweaks to the code can 
cause the error to disappear, I imagine it could be tricky to fix, but 
at the least there should probably be a warning in the docs that some 
kinds of anootation boxes won't work with some kinds of arrows when 
the text is too close to the annotated point.

	Any ideas?

Thanks.
-- 
Brendan Barnwell
"Do not follow where the path may lead.  Go, instead, where there is 
no path, and leave a trail."
    --author unknown