matplotlib-users Mailing List for matplotlib

Mark,
It sounds like what you want axis('scaled') to do is nothing other than
gca().set_aspect(1, adjustable='box')
draw_if_interactive()
I think this is a bit out of character with things like axis('equal'). 
Part of this character is that automatic things are turned on, so that 
going back and forth between axis('equal') and axis('scaled') switches 
back and forth between the same two plots; the result is not 
history-dependent.
At your request (between the 0.87.7 and 0.90 releases), I put in a 
little bit of history-dependence by making axis('scaled') call to
 self.set_autoscale_on(False) # Req. by Mark Bakker
after the set_aspect() call. This means that you can get the behavior 
you want simply by changing your example to
from pylab import *
plot([1,2,3],[1,2,1])
axis('scaled')
axis([1,2,1,2]) # define new axis limits
Is this good enough? Do you really need to be able to set the axis 
limits *before* the call to axis('scaled')? If so, then I am inclined 
to make this a separate option for the axis command, because I think the 
present behavior of axis('scaled') is sensible in the context of the 
other existing options.
Eric
Mark Bakker wrote:
> Eric -
> 
> I just installed version 0.90 on my windows machine and it seems that 
> axis('scaled') doesn't work properly yet.
> I thought axis('scaled') will change the axes such that the aspect ratio 
> is equal WITHOUT changing the limits on the axes.
> A simple example shows that this goes wrong (I thought this used to work):
> 
> from pylab import *
> plot([1,2,3],[1,2,1])
> axis([1,2,1,2]) # define new axis limits
> axis('scaled')
> 
> And now Python comes back with ( 1.0, 3.0, 0.80000000000000004, 2.0), 
> which are the limits of the original plot command obtained using 
> autoscale_view.
> I think this is an easy fix in the axis function of axes.py.
> Here you do an autoscale_view, which shouldn't be done in the 'scaled' 
> option.
> I think you only need to change the indicated line below.
> 
> Thanks,
> 
> Mark
> 
> def axis(self, *v, **kwargs):
> '''
> Convenience method for manipulating the x and y view limits
> and the aspect ratio of the plot.
> 
> kwargs are passed on to set_xlim and set_ylim -- see their 
> docstrings for details
> '''
> if len(v)==1 and is_string_like(v[0]):
> s = v[0].lower()
> if s=='on': self.set_axis_on()
> elif s=='off': self.set_axis_off()
> elif s in ('equal', 'tight', 'scaled', 'normal', 'auto', 
> 'image'):
> self.set_autoscale_on(True)
> self.set_aspect('auto')
> if s!= 'scaled': self.autoscale_view() # THIS LINE WAS 
> CHANGED BY ADDING THE IF STATEMENT
> self.apply_aspect()
> if s=='equal':
> self.set_aspect('equal', adjustable='datalim')
> elif s == 'scaled':
> self.set_aspect ('equal', adjustable='box', anchor='C')
> self.set_autoscale_on(False) # Req. by Mark Bakker
> elif s=='tight':
> self.autoscale_view (tight=True)
> self.set_autoscale_on(False)
> elif s == 'image':
> self.autoscale_view(tight=True)
> self.set_autoscale_on(False)
> self.set_aspect('equal', adjustable='box', anchor='C')
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Thanks for doing this, the wx back-ends are a bit neglected at the moment.
Which version of wxPython did you test this all on? We really need some 
work/testing with 2.8.*, I now there are some issues on OS-X, but I 
haven't tried it anywhere else yet.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

On 2/14/07, Darren Dale <dd...@co...> wrote:
> What Ewald is trying to do used to work. The idea is not to work
> interactively, but to run a script and have the plots render in stages, the
> next stage begins when the current windows are closed. I know we have users
> who take advantage of this behavior for presentations.
This was always an unsupported use of show. The FAQ entry
 http://matplotlib.sourceforge.net/faq.html#SHOW
states in bold:
 IMPORTANT: show should called at most once per script and it should be the
 last line of your script. At that point, the GUI takes control of
the interpreter.
 If you want to force a figure draw, use draw instead.
That is worked in some cases can be considered an accident of the
backend and possibly GUI version.
That said, I would like to support this use case, essentially a pause
until some user input is given. Lots of people want it and it is a
useful thing. This came up again back in October. Nadia at STScI
worked on this and I think she thought she had a solution for blocking
calls in a threaded environment. Maybe she can provide some input
here.
JDH

On 2/14/07, David Clark (Lists) <dd...@la...> wrote:
> I'm working on a GUI with wxPython to display several traces of data.
> Using a checkbox, I would like to be able to turn traces on the plot on
> and off. I have managed to find the right methods to turn the whole
> axes on and off, but not individual traces. Any help would be appreciated.
Everythong that draws into a figure (Axes, Text, Line2D, Polygon,
etc...) all derive from Artist which has a visible property. So you
can turn anything off/on with
o.set_visible(True|False)
JDH

On 2/14/07, Sture Lygren <st...@ro...> wrote:
> Thank's a lot for your informative answer. I've solved the issue now using
> WXAgg as backend. WX was way too slow (plotting two graphs with 8000
> datapoints each)
Happy to know it have solved your issue :-)
NG

Hi,
Thank's a lot for your informative answer. I've solved the issue now using
WXAgg as backend. WX was way too slow (plotting two graphs with 8000
datapoints each)
regards,
Sture
>> I've been trying to use matplotlib from boa constructor (on windows,
>> running enthon-python2.4-1.0.0 and boa-constructor 0.4.4). For test
>> purpose I have a single button-event call this function:
>>
>> def testPlot():
>> plot([1,2,3])
>> show()
>>
>> Everything is fine for the first event - button fires the function and
>> a plot-window is showing. Killing this window and have a second go at
>> the plot at first seems to work but the window can not be closed and
>> when I try to move said window the whole application crash.
>
> There is a conflict between the GUI library used by boa constructor
> (wxWidgets/wxPython) and the one used by default by matplotlib when
> you run the show() command (Tk).
>
> Each of these two libraries run an event loop, handling all your
> keyboard and mouse inputs. When you start your application, wxWidgets
> has control. When you run show(), Tk takes control and displays your
> matplotlib chart. But when you close the chart window, Tk keeps
> control, so your application freezes.
>
> The solution is to use another backend, compatible with wxpython. Try
> backend WX or WXAgg.
>
> At the top of your script (before import pylab), add this:
> import matplotlib
> matplotlib.use('WX')
>
> or:
> import matplotlib
> matplotlib.use('WXAgg')
>
> More explanations here: http://matplotlib.sourceforge.net/backends.html
>
> For reference, here is information provided on matplotlib's web site:
> http://matplotlib.sourceforge.net/installing.html
> There are known conflicts with some of the backends with some python
> IDEs such as pycrust, idle. If you want to use matplotlib from an IDE,
> please consult backends for compatibility information. You will have
> the greatest likelihood of success if you run the examples from the
> command shell or by double clicking on them, rather than from an IDE.
> If you are interactively generating plots, your best bet is TkAgg from
> the standard python shell or ipython.
>
> Good luck!
>
> -- Nicolas Grilly
>
>
-- 
Sture Lygren
Computer Systems Administrator
Andoya Rocket Range
Work: +4776144451 / Fax: +4776144401

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- --
David D. Clark
Electrical Engineer
P-23, Neutron Science and Technology
e-mail mailto:dd...@la...
GPG Public key 0x018D6523 available at http://www.us.pgp.net
http://www.gnupg.org has information about public key cryptography
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF01UANu7GcwGNZSMRAoXAAKCXUTOg6rJQ+/uWpA9+y9lMvXjDcACgj2Qh
fVgbxatBaf5cT8GsNc3eB70=
=8ZDP
-----END PGP SIGNATURE-----

Okay, I'll answer my own question. After looking through the code, it appe=
ars I have to do a xgridlines - not gridlines, like:=0A=0Aglines =3D getp(g=
ca(), 'xgridlines')=0A=0A> =0A> Hi list,=0A> =0A> The tutorial indicated th=
at I can use gca to get at the grid =0A> by doing a:=0A> =0A> glines =3D ge=
tp(gca(), 'gridlines')=0A> but when I do that, I get a "Subplot instance ha=
s no =0A> attribute "get_gridlines".=0A> =0A> How do I get to the grid obje=
ct?=0A> =0A> Thanks,=0A> =0A> --=0A> John Henry=0A=0A =0A--=0AJohn Henry=
=0A=0A

Hi list,=0A=0AThe tutorial indicated that I can use gca to get at the grid =
by doing a:=0A=0Aglines =3D getp(gca(), 'gridlines')=0Abut when I do that, =
I get a "Subplot instance has no attribute "get_gridlines".=0A=0AHow do I g=
et to the grid object?=0A=0AThanks,=0A =0A--=0AJohn Henry=0A=0A

I just downloaded the 0.9 binary and did some testing and also updated 
all the wx examples to use the new wx namespace (i.e. change from "from 
wxPython.wx import *" to "import wx".
dynamic_demo_wx.py
- changed name space using Boa's conversion tool
- moved the timer stuff to __init__, saved a reference and stop the 
timer on close, so that this shuts down correctly.
dynamic_demo_wxagg2.py
- changed name space using Boa's conversion tool
- complains about wxmsw26uh_vc.dll, but runs if one clicks on OK
dynamic_demo_wxagg.py
- changed name space using Boa's conversion tool
- complains about wxmsw26uh_vc.dll, but runs if one clicks on OK
embedding_in_wx.py
- changed name space using Boa's conversion tool
- screen update/refresh is for some reason very slow
embedding_in_wx2.py
- changed name space using Boa's conversion tool
- complains about wxmsw26uh_vc.dll, but runs if one clicks on OK
embedding_in_wx3.py
- changed name space using Boa's conversion tool
- manually made changes regarding XRC as it is not handled by the 
conversion tool
- can't get it to work, as think it is because 
"data/embedding_in_wx3.xrc" is not found - it is not included in the zip?!
embedding_in_wx4.py
- changed name space using Boa's conversion tool
- complains about wxmsw26uh_vc.dll, but runs if one clicks on OK
simple3d_oo.py
- changed name space using Boa's conversion tool
- complains about wxmsw26uh_vc.dll, but runs if one clicks on OK
If someone could take the enclosed and maybe create an updated examples.zip
When a build for wxPython 2.8 is available I will do some more testing, 
especially with regards to py2exe packaging.
Werner

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I'm working on a GUI with wxPython to display several traces of data.
Using a checkbox, I would like to be able to turn traces on the plot on
and off. I have managed to find the right methods to turn the whole
axes on and off, but not individual traces. Any help would be appreciated.
Thanks,
Dave
- --
David D. Clark
Electrical Engineer
P-23, Neutron Science and Technology
e-mail mailto:dd...@la...
GPG Public key 0x018D6523 available at http://www.us.pgp.net
http://www.gnupg.org has information about public key cryptography
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF0zh9Nu7GcwGNZSMRAgw3AKCuak5AJhp9df71nbZ+/QDDZc86OQCdHVBA
YRXrvtwMQqObyfFA08NKIBw=
=2Th4
-----END PGP SIGNATURE-----

> I've been trying to use matplotlib from boa constructor (on windows,
> running enthon-python2.4-1.0.0 and boa-constructor 0.4.4). For test
> purpose I have a single button-event call this function:
>
> def testPlot():
> plot([1,2,3])
> show()
>
> Everything is fine for the first event - button fires the function and
> a plot-window is showing. Killing this window and have a second go at
> the plot at first seems to work but the window can not be closed and
> when I try to move said window the whole application crash.
There is a conflict between the GUI library used by boa constructor
(wxWidgets/wxPython) and the one used by default by matplotlib when
you run the show() command (Tk).
Each of these two libraries run an event loop, handling all your
keyboard and mouse inputs. When you start your application, wxWidgets
has control. When you run show(), Tk takes control and displays your
matplotlib chart. But when you close the chart window, Tk keeps
control, so your application freezes.
The solution is to use another backend, compatible with wxpython. Try
backend WX or WXAgg.
At the top of your script (before import pylab), add this:
import matplotlib
matplotlib.use('WX')
or:
import matplotlib
matplotlib.use('WXAgg')
More explanations here: http://matplotlib.sourceforge.net/backends.html
For reference, here is information provided on matplotlib's web site:
http://matplotlib.sourceforge.net/installing.html
There are known conflicts with some of the backends with some python
IDEs such as pycrust, idle. If you want to use matplotlib from an IDE,
please consult backends for compatibility information. You will have
the greatest likelihood of success if you run the examples from the
command shell or by double clicking on them, rather than from an IDE.
If you are interactively generating plots, your best bet is TkAgg from
the standard python shell or ipython.
Good luck!
-- Nicolas Grilly

Hello,
I have been working with Mlib and networkX to create a server which 
listens for connections and based on the message it receives, it updates 
and shows a graph. These are great tools but one thing has come up: when 
the graph has been updated and the control goes back so listening 
socket.accept(), the GUI does not refresh anymore. This means that the 
whole GUI turns into gray if some other window is brought on top of it. 
Also it isn't possible to close the GUI window from the 'X' button etc. 
However, when a new message arrives to the server, the GUI is updated but 
then the refreshes are left undone until the next message and this cycle 
repeats over and over.
If I change my program so that after the first draw & show the program 
runs exit, the GUI is refreshed all the time and thus works like it 
should. Any suggestions? I found out that someone else had the same 
problem:
http://article.gmane.org/gmane.comp.python.matplotlib.general/5550/match=ipython+gui+refresh
My system is FC4 with networkX-0.33, Mlib-0.90.0, python 2.4.3, ipython 
0.7.2. I have tried TkAgg, GTKAgg and WxAgg but they all give the same 
result. With GTK backend even the graph doesn't show up so. Maybe ipython 
has something to do with this? My program doesn't have a proper GUI so 
only the graph is shown graphically. That is why I haven't looked at 
embedding Mlib stuff.
Here are two simple examples how the problem could be reproduced. The 
window is not refreshed until the sleep has run out.
1)
import networkx as NX
import pylab as P
import time
G=NX.Graph()
G.add_edge(1,2)
G.add_edge(2,3)
NX.draw(G)
time.sleep(5)
2)
from pylab import *
import time
gcf().text(0.5, 0.95, 'Distance Histograms by Category is a really long 
title')
show()
time.sleep(5)
Thanks for any answers or suggestions!
Tomi Hautakoski
th...@ik...
 When I play in the sandbox, the cat covers me up!

I have a follow-up on my previous emai.
I don't think we should do an autoscale_view() for axis('equal') either.
For axis('equal') only the limits of either the x or y axis are adjusted
(enlarged really) until the aspect ratio is equal.
Not sure about the others. Do we ever need to do it?
Mark

Eric -
I just installed version 0.90 on my windows machine and it seems that
axis('scaled') doesn't work properly yet.
I thought axis('scaled') will change the axes such that the aspect ratio is
equal WITHOUT changing the limits on the axes.
A simple example shows that this goes wrong (I thought this used to work):
from pylab import *
plot([1,2,3],[1,2,1])
axis([1,2,1,2]) # define new axis limits
axis('scaled')
And now Python comes back with (1.0, 3.0, 0.80000000000000004, 2.0), which
are the limits of the original plot command obtained using autoscale_view.
I think this is an easy fix in the axis function of axes.py.
Here you do an autoscale_view, which shouldn't be done in the 'scaled'
option.
I think you only need to change the indicated line below.
Thanks,
Mark
 def axis(self, *v, **kwargs):
 '''
 Convenience method for manipulating the x and y view limits
 and the aspect ratio of the plot.
 kwargs are passed on to set_xlim and set_ylim -- see their
docstrings for details
 '''
 if len(v)==1 and is_string_like(v[0]):
 s = v[0].lower()
 if s=='on': self.set_axis_on()
 elif s=='off': self.set_axis_off()
 elif s in ('equal', 'tight', 'scaled', 'normal', 'auto',
'image'):
 self.set_autoscale_on(True)
 self.set_aspect('auto')
 if s!= 'scaled': self.autoscale_view() # THIS LINE WAS
CHANGED BY ADDING THE IF STATEMENT
 self.apply_aspect()
 if s=='equal':
 self.set_aspect('equal', adjustable='datalim')
 elif s == 'scaled':
 self.set_aspect('equal', adjustable='box', anchor='C')
 self.set_autoscale_on(False) # Req. by Mark Bakker
 elif s=='tight':
 self.autoscale_view(tight=True)
 self.set_autoscale_on(False)
 elif s == 'image':
 self.autoscale_view(tight=True)
 self.set_autoscale_on(False)
 self.set_aspect('equal', adjustable='box', anchor='C')

On Wednesday 14 February 2007 6:59:18 am George Nurser wrote:
> On 14/02/07, Ewald Zietsman <ewa...@gm...> wrote:
> > Hi All,
> >
> > I have a slight problem using matplotlib 0.87.7. I'm using Ubuntu 6.10
> > and installed mpl from source. I'm running numpy 1.01, also installed
> > from source.
> >
> > If I run the script below, the first plot shows fine. When I close it the
> > second plot should display but it doesn't. I can only get the first plot
> > to show. Thereafter the plot command doesn't seem to work. I tried
> > reinstalling matplotlib. That didn't work. This works fine if I type it
> > into ipython. It also works on my computer running FC5.
> >
> > Any help will be greatly appreciated.
> >
> > -Ewald
> >
> > # Sample script
> > from pylab import *
> > t = arange(10)
> > f = t*t
> > plot(t,f)
> > show()
> > plot(t,f)
> > show()
>
> Ewald,
>
> It may be that what you are trying should work.
>
> However, I believe that for interactive work it is recommended to use
> ipython -pylab unless you are using the TkAgg backend.
What Ewald is trying to do used to work. The idea is not to work 
interactively, but to run a script and have the plots render in stages, the 
next stage begins when the current windows are closed. I know we have users 
who take advantage of this behavior for presentations.
Darren

On 14/02/07, Ewald Zietsman <ewa...@gm...> wrote:
> Hi All,
>
> I have a slight problem using matplotlib 0.87.7. I'm using Ubuntu 6.10 and
> installed mpl from source. I'm running numpy 1.01, also installed from
> source.
>
> If I run the script below, the first plot shows fine. When I close it the
> second plot should display but it doesn't. I can only get the first plot to
> show. Thereafter the plot command doesn't seem to work. I tried reinstalling
> matplotlib. That didn't work. This works fine if I type it into ipython. It
> also works on my computer running FC5.
>
> Any help will be greatly appreciated.
>
> -Ewald
>
> # Sample script
> from pylab import *
> t = arange(10)
> f = t*t
> plot(t,f)
> show()
> plot(t,f)
> show()
>
Ewald,
It may be that what you are trying should work.
However, I believe that for interactive work it is recommended to use
ipython -pylab unless you are using the TkAgg backend. You select
this in your matplotlibrc file (it should go into ~/.matplotlib)
OR
(see http://matplotlib.sourceforge.net/faq.html) you can do the use
command before importing pylab, as described at
http://matplotlib.sourceforge.net/backends.html
 >>> import matplotlib
 >>> matplotlib.use('TkAgg')
 >>> from pylab import *
Note that if you are using an IDE like pycrust, ipython -pylab,
pythonwin, or IDLE, pylab may have already been loaded, and subsequent
calls to use or from pylab import * will have no effect unless you
explicitly force a module reload.
HTH. George Nurser.

Hi All,
I have a slight problem using matplotlib 0.87.7. I'm using Ubuntu 6.10 and
installed mpl from source. I'm running numpy 1.01, also installed from
source.
If I run the script below, the first plot shows fine. When I close it the
second plot should display but it doesn't. I can only get the first plot to
show. Thereafter the plot command doesn't seem to work. I tried reinstalling
matplotlib. That didn't work. This works fine if I type it into ipython. It
also works on my computer running FC5.
Any help will be greatly appreciated.
-Ewald
# Sample script
from pylab import *
t = arange(10)
f = t*t
plot(t,f)
show()
plot(t,f)
show()

Hello,
I've been trying to use matplotlib from boa constructor (on windows,
running enthon-python2.4-1.0.0 and boa-constructor 0.4.4). For test
purpose I have a single button-event call this function:
def testPlot():
	plot([1,2,3])
	show()
Everything is fine for the first event - button fires the function and
a plot-window is showing. Killing this window and have a second go at
the plot at first seems to work but the window can not be closed and
when I try to move said window the whole application crash.
So - why is this happening?
regards,
Sture
-- 
Sture Lygren
Computer Systems Administrator
Andoya Rocket Range
Work: +4776144451 / Fax: +4776144401

I am having trouble with axes and grids in the y-direction.=0A=0AI have a 3=
 rows x 2 colums figure and I like to have 5 major Y divisions or 4 grid li=
nes for each of the graphs. 5 of the 6 graphs came out properly. For ins=
tance, for a Ymin=3D12, Ymax=3D17, I get grid lines at y=3D13, 14, 15, and =
16. However, the 6th one isn't right. For a Ymin=3D-5 and Ymax=3D5, I g=
et grid lines at y=3D-4, -2, 0, 2, 4 (but the origin does starts with y=3D-=
5). I want to have only 4 grid lines (at y=3D-3, -1, +1, 3). I tried man=
y settings but the result is the same. =0A=0AWhat should I do to get only=
 4 grid lines in the y-direction?=0A=0ARegards,=0A =0A--=0AJohn Henry=0A=0A

I asked some help last week.
I post here the solution to my problem since I believe it's something of
general interest.
A figure is generated and the user can change the size of the canvas (in
inches) interactively, as if we are zooming in and out the canvas.
This is particularly useful when you are drawing figures that can have few
or many subplots.
I couldn't manage to get this working with a resize so the trick is that
every time we destroy and create the canvas.
Cheers.
-------------------------------------------------------------
import wx, wxmpl
from numpy import *
class PanelWScrolledWindow(wx.ScrolledWindow):
	def __init__(self,parent):
		wx.ScrolledWindow.__init__(self, parent)
		self.mainsizer = wx.BoxSizer(wx.VERTICAL)
		self.BTNsizer = wx.BoxSizer(wx.HORIZONTAL)
		self.width, self.heigth = 3, 6
		BTNsmall = wx.Button(self, -1, "Smaller FIG")
		BTNbig = wx.Button(self, -1, "Bigger FIG")
		self.Bind(wx.EVT_BUTTON, self.onBTNbig, BTNbig)
		self.Bind(wx.EVT_BUTTON, self.onBTNsmall, BTNsmall)
		self.BTNsizer.Add (BTNsmall, 0, wx.GROW|wx.ALL, 1)
		self.BTNsizer.Add (BTNbig, 0, wx.GROW|wx.ALL, 1)
		#Note that in a real world you want the button to be outside
the scrolledwindow
		self.mainsizer.Add (self.BTNsizer, 0, wx.GROW|wx.ALL, 1)
		self.CreateCanvas()
	def CreateCanvas(self, size=(2,4)):
		try:
			self.canvas.Destroy()
		except:
			pass
		
		self.canvas = wxmpl.PlotPanel(self, -1, size)
		self.SetScrollbars(20, 20, size[0]/20, size[1]/20)
		self.mainsizer.Add (self.canvas, 1, wx.GROW|wx.ALL, 1)
		self.SetSizer(self.mainsizer)
		self.FitInside()
		
	def onBTNbig(self,event):
		self.heigth += 1
		self.width +=1
		self.CreateCanvas(size=(self.width,self.heigth))
		plot_simple(self.canvas.get_figure())
	def onBTNsmall(self,event):
		self.heigth -= 1
		self.width -=1
		self.CreateCanvas(size=(self.width,self.heigth))
		plot_simple(self.canvas.get_figure())
class MyFrame(wx.Frame):
	def __init__(self, parent, title):
		wx.Frame.__init__(self, parent)
		self.nb = wx.Notebook(self)
		self.PageOne = PanelWScrolledWindow(self.nb)
		self.PageTwo = wx.Panel(self.nb)
		self.nb.AddPage(self.PageOne, "PageOne")
		self.nb.AddPage(self.PageTwo, "PageTwo")
def plot_simple(fig):
	t = arange(0.0, 2.0, 0.01)
	s = sin(2*pi*t)
	c = cos(2*pi*t)
	
	axes = fig.gca()
	axes.plot(t, s, linewidth=1.0)
	axes.plot(t, c, linewidth=1.0)
	
	axes.set_xlabel('time (s)')
	axes.set_ylabel('voltage (mV)')
	axes.set_title('About as simple as it gets, folks')
	axes.grid(True)
#here we start
app = wx.PySimpleApp()
frm = MyFrame(None, "Test")
frm.SetSize((800,600))
frm.Show()
app.SetTopWindow(frm)
app.MainLoop()