On 10/01/2010 02:01 PM, Fernando Perez wrote:
Hey Ryan,
On Fri, Oct 1, 2010 at 6:27 AM, Ryan Mayrma...@gmail.com wrote:
On Fri, Oct 1, 2010 at 1:05 AM, Fernando Perezfperez@gmail.com wrote:
This manifested itself in some more complex MPL code that had multiple
events not
On Mon, Oct 4, 2010 at 6:13 AM, Michael Droettboom md...@stsci.edu wrote:
The problem is when callbacks create cyclical references (which your
example does not). If the Handler class in your example needed to
update the figure or canvas in some way in the callback (which is a
common usage
On 10/01/2010 08:01 AM, Fernando Perez wrote:
In any case, if my logic is flawed (quite likely, since I imagine M.
D. had a good look at this), it might be worth adding a
.. warning::
section about this pattern to the event docs:
On Sun, Oct 3, 2010 at 2:05 PM, Eric Firing efir...@hawaii.edu wrote:
section about this pattern to the event docs:
http://matplotlib.sourceforge.net/users/event_handling.html
Done in 8723.
Thanks!
Cheers,
f
--
Howdy,
I spent a while chasing my tail today with some event handling code
until I tried backtracking from SVN matplotlib back to 0.99.1 (the one
in ubuntu 10.04) and the problem went away.
I'm attaching a script that reproduces the problem with a full
description in the docstring, reproduced
On Fri, Oct 1, 2010 at 1:05 AM, Fernando Perez fperez@gmail.com wrote:
This manifested itself in some more complex MPL code that had multiple
events not working when run inside ipython, but working OK outside of
ipython. Fortunately, the small self-contained example demonstrates
the
Hey Ryan,
On Fri, Oct 1, 2010 at 6:27 AM, Ryan May rma...@gmail.com wrote:
On Fri, Oct 1, 2010 at 1:05 AM, Fernando Perez fperez@gmail.com wrote:
This manifested itself in some more complex MPL code that had multiple
events not working when run inside ipython, but working OK outside of
