On Sat, Nov 13, 2010 at 9:23 AM, Michiel de Hoon <mjldeh...@yahoo.com> wrote: > Thanks for your reply. > But nowadays drawing is done through draw_idle, so we don't trigger > additional drawing even if interactive is True. In your example, if run as a > script, there is no drawing until a call to show() is made, regardless of > whether interactive is True or False.
I see. I wasn't appreciating your point and had neglected to consider the idle drawing handling. Are we sure this will save us. Ie if we have a scirpt like # some plotting commands ... # some expensive non GUI computation ... # some update to plot above ... Would we not run the risk that the GUI is idle in the non GUI computation and therefore trigger a draw in it's thread, and then do redraws again after the update code? I did run some tests and confirmed what you said, that with the idle handling the repeat calls to pyplot commands did not generate extra calls (except in qtagg in which I suspect the idle handling has not been implemented. Are you proposing that we can get rid of the interactive setting entirely, always call draw on pyplot commands, and let the idle handler save us from doing repeated draws? ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
