matplotlib-users Mailing List for matplotlib

>>>>> "Flavio" == Flavio Codeco Coelho <fcc...@fi...> writes:

    Flavio> John, The following example works ok with WXAgg (Hoorray!)
    Flavio> but the exponent 4 at the end of the expression does not
    Flavio> show up (with or without brackets).

Yes, there is a bug in the parser for over/under subscripts.  I think
I have the fix for it, but haven't been able get it done yet. 
   
    Flavio> Also, an anoying thing is the need for spaces around TeX
    Flavio> markup.  The same expression does not get formatted by
    Flavio> mathtext if you remove the spaces. This is going to
    Flavio> confuse TeX users since LaTeX doesn't need spaces.

Yes, at the least a \/ symbol would be nice.

    Flavio> one last thing: after you close the WXAgg figure, the
    Flavio> execution does not return to the interpreter. This does
    Flavio> not happen on GTK.

OK, thanks for letting me know.

JDH

>>>>> "Engelsma," == Engelsma, Dave <D.E...@La...> writes:

    Dave> Hello - I''ve got a wxDialog where, among other
    Dave> controls, I have a wxList and a
    Dave> FigureCanvasWx. Depending on what single item is
    Dave> selected in the wxList, the FigureCanvasWx should show
    Dave> the appropriate graph. It's important that the
    Dave> matplotlib-generated graph stay in the dialog along
    Dave> with the other controls (I don't want to generate a
    Dave> separate frame for the graph).

I'm not a wx guru, so this may not be the best way, but it I think it
is a pretty good way.  Instead of putting a FigureCanvasWX in your,
use a wxPanel instead.  Maintain a list of FigureCanvasAgg and use
them to draw your figures.  Transfer these to the wxPanel using string
and bitmap methods.  This is effectively what wxagg does.  The main
difference is that you will have one canvas and a list of
FigureCanvasAggs.

You can get the width and height of the figure you need to draw with
    
   

Suppose agg below is an FigureCanvasAgg instance

        agg.draw()
        s = agg.tostring_rgb()  
        l,b,w,h = agg.figure.get_window_extent().get_bounds()
        image = wxEmptyImage( w,h )
        image.SetData(s)
        bitmap = image.ConvertToBitmap()

You can then transfer the bitmap to the wxpanel.  If you want to do
all the 'draw' calls upfront so you don't have to repeatedly draw if
the user selects one figure, then another, then the original, that
will be fine.

Agg is a pretty fast renderer, which may more than make up for the
performance hit of having to go through the string->bitmap->canvas.

Let me know how it goes.

JDH

>>>>> "H=E9ctor" =3D=3D H=E9ctor Villafuerte D <hec...@te...=
m.gt> writes:
    H=E9ctor> savefig("c:\\tmp\\%s_%s" % (tel,table)) File
    H=E9ctor> "C:\Python23\Lib\site-packages\matplotlib\matlab.py", line
    H=E9ctor> 1115, in savefig manager.canvas.print_figure(*args,
    H=E9ctor> **kwargs) File
    H=E9ctor> "C:\Python23\Lib\site-packages\matplotlib\backends\backend_=
agg.py",
    H=E9ctor> line 419, in print_figure
    H=E9ctor> self.renderer._renderer.write_png(filename) IOError: could
    H=E9ctor> not open file

This is a new one; I think the file is not writable and it is not a
matplotlib problem per se.  Is it possible that C:\\tmp does not
exist?

You may want to try something along the lines of

import os

...snip...
dirname =3D 'c:\\tmp'
fname =3D os.path.join(dirname, '%s_%s' % (tel,table))
print 'dir exists', os.path.exists(dirname)
print 'filename', fname

file(fname, 'w').write('test\n')

and see if you can see what is going wrong.

JDH

>>>>> "H=E9ctor" =3D=3D H=E9ctor Villafuerte D <hec...@te...=
m.gt> writes:

    H=E9ctor> 720, in __init__ MultipleLocator.__init__(self,
    H=E9ctor> base*SEC_PER_MIN) NameError: global name 'SEC_PER_MIN' is
    H=E9ctor> not defined

This is a bug in ticker that will be fixed in the next bugfix
release.  If you want to fix it yourself now, edit
matplotlib/ticker.py and add SEC_PER_MIN to the list of things
imported from the dates module.  Ie,

from dates import EpochConverter, SEC_PER_HOUR, SEC_PER_DAY, SEC_PER_WEEK=
, \
     SEC_PER_MIN

The pcolor_demo.py and pcolor_demo2.py show somewhat different results:

------------
from matplotlib.matlab import *

def fun3(x,y):
    return (1- x/2 + x**5 + y**3)*exp(-x**2-y**2)

xi=arange(-3.0, 3.0, 0.05)
yi=arange(-3.0, 3.0, 0.05)
[Xi,Yi]=meshgrid(xi,yi);
Zi=fun3(Xi,Yi)    

if 1:
   cMap = ColormapJet(256)
   imshow(Zi, cMap)
   gca().set_image_extent(-3, 3, -3, 3)
else:
   pcolor(Xi, Yi, Zi, shading='flat')

show()


-------------


The y axis seem to be inverted on imshow when compared to pcolor. Was 
this intentional?