On Mon, Sep 15, 2008 at 07:38:01PM -0400, Paul Kienzle wrote:
> It does not poll.

> draw_idle() triggers a timer with a 5ms delay.  This timer is reset for
> each draw_idle() call.  At timeout the timer is restarted if there are more
> events on the wx event queue, otherwise the graph is rendered.  This means
> you can do as many draw_idle commands as you want while processing your
> data, but the expensive rendering will only happen once.

OK, very nice. This is indeed a very efficient pattern for dealing with
too agressive refresh. I've seen it used with a lot of success in many
places. Thanks for enlighting me on this. I guess I could (should?) have
looked at the code base.

Gaƫl

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to