It works. Thanks a lot for explanation, Ben.
Stepan
On Fri, Nov 7, 2014 at 6:37 PM, Benjamin Root wrote:
> Figured it out! The instance of Test() isn't being retained anywhere, so
> when it goes out of scope, the garbage collector eventually gets it. The
> fact that it works in py3k is likely a
Sorry I'm lost in the discussion.
What is the relation between the weak references in callback registry and
moving stuff to the figure manager?
Federico
On 7 Nov 2014 14:13, "Thomas Caswell" wrote:
> I am also beginning to like the idea of hanging all of these things off of
> FigureManager objec
I am also beginning to like the idea of hanging all of these things off of
FigureManager objects. We have them around, but they are really only used
in pyplot (which is a shame) and seems a natural place to put all of these
aggregation type objects (list of animations, the toolbar stuff, the
navig
The old-style classes are because mpl pre-dates new-style classes. On
master all classes now inherit from object (as of about 3 weeks ago
https://github.com/matplotlib/matplotlib/pull/3662)
On Fri Nov 07 2014 at 2:02:15 PM Brendan Barnwell
wrote:
> On 2014-11-07 09:37, Benjamin Root wrote:
>
There have been some discussion of adding an fig.animations list (a la
ax.images, ax.artists), and have a fig.add_animation() method. We could
then update the animation code to add itself to the given figure to make
this work for all existing code. Maybe it would be a nice tie-in with the
updates t
On 2014-11-07 09:37, Benjamin Root wrote:
> Figured it out! The instance of Test() isn't being retained anywhere, so
> when it goes out of scope, the garbage collector eventually gets it. The
> fact that it works in py3k is likely a coincidence as the garbage
> collector would eventually have clean
This came up regrading sliders a while ago:
https://github.com/matplotlib/matplotlib/issues/3105 and is one of the
persistent gotchas with animation code.
Tom
On Fri Nov 07 2014 at 12:38:28 PM Benjamin Root wrote:
> Figured it out! The instance of Test() isn't being retained anywhere, so
> when
Figured it out! The instance of Test() isn't being retained anywhere, so
when it goes out of scope, the garbage collector eventually gets it. The
fact that it works in py3k is likely a coincidence as the garbage collector
would eventually have cleaned it up at some point. I don't know the
scoping/g
Thanks for the tip. However, subclassing from object didn't help.
--
View this message in context:
http://matplotlib.1069221.n5.nabble.com/Problem-with-event-handling-in-matplotlib-in-tkinter-tp44302p44315.html
Sent from the matplotlib - users mailing list archive at Nabble.com.
--
I think it is because your Test() class is not subclassed from "object". Of
course, I have no clue why that would be an issue, but I have seen stranger
things when not subclassing from object.
On Fri, Nov 7, 2014 at 9:31 AM, rouckas wrote:
> I have a little update on the issue: I tried it with d
I have a little update on the issue: I tried it with different versions of
python and matplotlib and it is still present in
python 2.7.6 + matplotlib 1.4.2
but it works as expected in
python 3.4.0 + matplotlib 1.4.2
Should this be reported as a bug in matplotlib 1.4.2 on python 2.7.6?
BTW, I not
Dear all,
I have a problem with using certain class methods as event handlers. In the
following example:
the method Test.on_press() is never executed. Only "clicked0" and "clicked1"
is printed when I click on the canvas. When i use pure matplotlib widgets
instead of tkinter embedding, the code
12 matches
Mail list logo
