matplotlib-users Mailing List for matplotlib

>>>>> "Andrew" == Andrew Straw <str...@as...> writes:

    Andrew> Hi All, I've added a new example, embedding_in_wx3, to
    Andrew> CVS.  From the docstring:

Coincidentally, I was also working on a different embedding_in_wx3
which shows how to use a custom toolbar, in response to another
question off list.  I changed the name submitted that as
embedding_in_wx4 :-)

    Andrew> John+Perry+whoever: the only matplotlib bug I found this
    Andrew> time is worked around by the line

    >> rcParams['image.origin'] = 'upper' # 'lower': nav toolbar
    >> problem -ADS

    Andrew> We should fix that at some point.

What was the bug?  I didn't notice any problems with lower.

BTW, the recommended way to set rc params in now with the rc command.
This was initially defined in matplotlib.matlab but I just moved it to
matplotlib.__init__.py to make it accessible to application
developers.  You can do

  matplotlib.rc('image', origin='lower')

and set multiple image params with multiple kwargs.

        self.toolbar.update() # Not sure why this is needed - ADS

This updates the Axes menu on the toolbar, which is needed if the
number of axes have changed.  Since the number of axes/subplots can
change after the figure/toolbar was created, this tells the toolbar to
update it's axes menu.

Another comment: try not to use x.resize in matplotlib examples,
because of the Numeric bug (did you get the emails Todd and I
exchanged regarding this?).  Numeric segfaulted for me when I
initially ran your example with the .resize command.

Note that matplotlib.mlab has the meshgrid command for building mesh
arrays from 2 1D vectors.  I replaced your code with

        x = numerix.arange(120.0)*2*numerix.pi/60.0
        y = numerix.arange(100.0)*2*numerix.pi/50.0
        self.x, self.y = meshgrid(x, y)
        z = numerix.sin(self.x) + numerix.cos(self.y)


Finally, there seems to be a figure size problem on linux: when I run
your example the figure window is too small and the image wraps.

Updates are in CVS - thanks for the submission.

JDH

Hi All,

I've added a new example, embedding_in_wx3, to CVS.  From the docstring:

> This is yet another example of using matplotlib with wx.  Hopefully
> this is pretty full-featured:
>
>   - both matplotlib toolbar and WX buttons manipulate plot
>   - full wxApp framework, including widget interaction
>   - XRC (XML wxWidgets resource) file to create GUI (made with XRCed)
>
> This was derived from embedding_in_wx and dynamic_image_wxagg.
>
> Thanks to matplotlib and wx teams for creating such great software!


John+Perry+whoever: the only matplotlib bug I found this time is worked 
around by the line

> rcParams['image.origin'] = 'upper' # 'lower': nav toolbar problem -ADS

We should fix that at some point.

Cheers!
Andrew

>>>>> "Brian" == Brian Sturk <bs...@ad...> writes:

    Brian> Is it possible to hide this in a plot?  I checked the FAQ,
    Brian> the archived messages, and the class lib docs and couldn't
    Brian> seem to find a way to.  ~brian

Which backend are you using?

JDH

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

Is it possible to hide this in a plot?  I checked the FAQ, the archived messages, and the class lib docs and couldn't seem to find a way to.

~brian