Re: [Matplotlib-users] dynamic image demo: suggestions sought

[Andrew S. <str...@as...>]

John Hunter wrote:

>>>>>>"John" == John Hunter <jdh...@ac...> writes:
>>>>>>            
>>>>>>
>
>    John> Haven't had a chance to test your example yet but hopefully
>    John> I can take a look tomorrow.  I haven't done much memory leak
>    John> testing against the _image module yet so this will be a good
>    John> opportunity.  I very recently rewrote _image.cpp using cxx.
>    John> I trust you have a fresh CVS checkout?
>
>Hi Andrew - found and fixed the memory leak.  Can't really call it a
>leak - more like a "memory gusher".  This was in the agg (and image)
>  
>
That makes a HUGE difference -- great!

>I made a number of comments in your example to point out places where
>you probably should be using matplotlib a little differently.
>  
>
OK, I see I have a lot of learning to do!  It's a lot cleaner now, but I 
left comments in for "common pitfalls to avoid when embedding in wx" 
enthusiasts.

>Please add it to CVS.
>  
>
Done.

>I liked the example so much I made an analogous one dynamic_image_gtk.
>  
>
Cool!  The GTK demo is nice because of the simplicity allowed by not 
embedding in a foreign GUI, but mainly using the matplotlib interface.

>It's faster than wxagg (13FPS vs 4FPS on my system) which is not
>surprising since gtkagg has extension code to transfer agg to the GUI
>canvas, 
>
It's even less surprising given that the wxagg app is driven by a timer 
callback set to run at 5 FPS! :)

>and doesn't flicker.  Very nice!  I would really like to get
>that wxagg flicker problem figured out, and the extension code
>added...  Did I hear you volunteering to be the wxagg maintainer :-)?
>  
>
Well, I'll hopefully have a chance to poke around in wxagg once in a 
while, but "maintainer" may be a bit grandiose for my time availability 
in the forseeable futurue...

Cheers!
Andrew