On Sun, Jan 29, 2012 at 3:41 AM, Jerzy Karczmarczuk <jerzy.karczmarc...@unicaen.fr> wrote: > > > There is one "rant", if you wish (of course, I am joking). > > The animation objects (FuncAnimation, etc.) are coded as they are, > probably sufficient for you. They are "one shot". But if you want to > stop and to resume your animation, they are not so well adapted.
Actually many thanks for this very interesting discussion! Just on Friday I came to this same conclusion while preparing some lecture material using animations. The lack of a clean pause/restart functionality is indeed problematic. Furthermore, closing a window that's running an animation, at least with the Qt backend, gave rise to a massive swarm of 'C++ object has been deleted' messages flooding the console where my ipython kernel had been started. One thing to keep in mind, if you go down the road of implementing a full-blown event loop for matplotlib, is how well it will play with existing event loops. Whenever an interactive GUI backend is running, there's already an event loop at work: that of the GUI toolkit. Integrating multiple event loops in the same process takes some delicate footwork if you don't want to end up with a nasty fight between the two. In any case, keep us posted on any progress! Best, f ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
