matplotlib-users Mailing List for matplotlib

I grabbed the CVS version and it works fine. Thanks for the help!
On Thursday 22 July 2004 12:45 pm, John Hunter wrote:
> >>>>> "Jeffery" == Jeffery D Collins <Jef...@ve...> writes:
>
> Jeffery> I'm getting an unexpected keyword error on 'extent'. Is
> Jeffery> this keyword available in the latest release or just in
> Jeffery> CVS?
>
> I must be getting soft in the head. I thought this was in the 0.60.2
> release, but you're right, it is not. Just checked the CHANGELOG.
> There is a way to do it in 0.60.2, but it is deprecated in CVS.
> Arggg.
>
> Your choices
>
> * wait for 0.61 (next week)
>
> * build from CVS - best solution. Fixes some problems with image
> extent plus image.origin='lower' reported earlier on
> matplotlib-users.
>
> * use the (deprecated in CVS/0.61)
>
> im = imshow(A)
> gca().set_image_extent(0, 25, 0, 25)
>
> Sorry for the confusions,
> JDH
-- 
-----------------------------------------------------------------
Jeffery D. Collins, Ph.D. Vexcel Corp.
Sr. Engineer 1690 38th St.
Voice: (303)583-0228 Boulder, CO 80301
Fax: (303)583-0246 vexcel.com

>>>>> "Jeffery" == Jeffery D Collins <Jef...@ve...> writes:
 Jeffery> I'm getting an unexpected keyword error on 'extent'. Is
 Jeffery> this keyword available in the latest release or just in
 Jeffery> CVS?
I must be getting soft in the head. I thought this was in the 0.60.2
release, but you're right, it is not. Just checked the CHANGELOG.
There is a way to do it in 0.60.2, but it is deprecated in CVS.
Arggg.
Your choices
 * wait for 0.61 (next week)
 * build from CVS - best solution. Fixes some problems with image
 extent plus image.origin='lower' reported earlier on
 matplotlib-users.
 * use the (deprecated in CVS/0.61)
 
 im = imshow(A)
 gca().set_image_extent(0, 25, 0, 25)
Sorry for the confusions,
JDH 
 

On Thursday 22 July 2004 12:03 pm, John Hunter wrote:
> >>>>> "Jeffery" == Jeffery D Collins <Jef...@ve...> writes:
>
> Jeffery> Is there a (convenient) matplotlib(v0.60.2) equivalent to
> Jeffery> the matlab imshow(x,y,A), where x and y are 2-tuples
> Jeffery> consisting of the bounds of the x and y axes,
> Jeffery> respectively? I have done some limited axis manipulation
> Jeffery> using the set_xticklabels and set_yticklabels methods,
> Jeffery> but that results in an unattractive plot.
>
I'm getting an unexpected keyword error on 'extent'. Is this keyword 
available in the latest release or just in CVS?
> If I am understanding you correctly
>
> >>> imshow(A, extent=(xmin, ymin, xmax, ymax))
>
> See also http://matplotlib.sf.net/matplotlib.matlab.html#-imshow and
> http://matplotlib.sf.net/examples/image_demo2.py.
>
> Hope this helps,
> JDH
-- 
-----------------------------------------------------------------
Jeffery D. Collins, Ph.D. Vexcel Corp.
Sr. Engineer 1690 38th St.
Voice: (303)583-0228 Boulder, CO 80301
Fax: (303)583-0246 vexcel.com

>>>>> "Jeffery" == Jeffery D Collins <Jef...@ve...> writes:
 Jeffery> Is there a (convenient) matplotlib(v0.60.2) equivalent to
 Jeffery> the matlab imshow(x,y,A), where x and y are 2-tuples
 Jeffery> consisting of the bounds of the x and y axes,
 Jeffery> respectively? I have done some limited axis manipulation
 Jeffery> using the set_xticklabels and set_yticklabels methods,
 Jeffery> but that results in an unattractive plot.
If I am understanding you correctly
 >>> imshow(A, extent=(xmin, ymin, xmax, ymax))
See also http://matplotlib.sf.net/matplotlib.matlab.html#-imshow and
http://matplotlib.sf.net/examples/image_demo2.py.
Hope this helps,
JDH

 Hello,
 I talked to the wxPython guys, asking them what's up with the
printing problems. They were very helpful. They gave me a link to an
unofficial build and I installed it. And now the print framework works
just fine, and more importantly, I'm able to print directly from
PyPlot without problems. So it seems that I'll stick with PyPlot after
all. Even if I had to modify it quite a bit in order to add plot marks
and other things, and it's not even close to matplotlib when it comes
to features. It's not something I want to do, but I have to :( If
anybody is interested, this is the link to the unnoficial wxPython
build:
 http://starship.python.net/crew/robind/wxPython/daily/20040717/
 Some API calls changed again ... unfortunately. But no too much.
 Hope this helps at least some of you. Again, thank you very much
for your help. I'll stick around here ... I'm sure that I'll find a
nice way to integrate matplotlib into my next product.
 Bogdan

Is there a (convenient) matplotlib(v0.60.2) equivalent to the matlab 
imshow(x,y,A), where x and y are 2-tuples consisting of the bounds of the x 
and y axes, respectively? I have done some limited axis manipulation using 
the set_xticklabels and set_yticklabels methods, but that results in an 
unattractive plot.
Thanks!
-- 
Jeff

I have just installed the latest CVS version of matplotlib. The EPS/PS=20=
backend works
well with latex commands and also the png backend, but the GUI does not=20=
work anymore.
When I ran any of the examples in the examples directory I get the=20
message
** (simple_plot.py:5668): WARNING **: Cannot open font file for font=20
Verdana 10
** (simple_plot.py:5668): WARNING **: Cannot open fallback font,=20
nothing to do
and python terminates. I have set the TTFPATH environment variable and=20=
I have
added the correct font path in font_manager.py which didn't help.
After severe problems with the gtk and pygtk installation via fink I=20
decided to do a manual
installation by hand and everything compiled without any problems.
Thanks in advance for any help
Michael
-------------------------------------------------------
Michael Oevermann
Technische Universit=E4t Berlin
Institut f=FCr Energietechnik
Fasanenstr. 89, 10623 Berlin, Germany
Phone: +49 (0) 30 314 22452
Fax: +49 (0) 30 314 22157
mailto: mic...@tu...
-------------------------------------------------------=

 Ok, I tested the toolbar again and this time everything is fine. I
guess that I was distracted by the fact that the "Pan" and "Zoom to
rectangle" buttons don't look as they are pressed when I press them :)
I mean, they don't change their visual appearance. They look like
normal buttons, but they should probably be toggle buttons. Apart from
that, everything else is fine. I don't need a recipe for JPG, i also
prefer PNG, i just signaled this because I thought it was a problem.
For printing ... I don't know :( I'll try to post a question to the wx
list and come back to you all if I receive a solution.
 Thank you very much for your support. Yes, again :)
 Bogdan
On 2004年7月22日 07:24:21 -0500, John Hunter
<jdh...@ac...> wrote:
> >>>>> "Marinescu" == Marinescu Bogdan-bmarine1 <bog...@fr...> writes:
> 
> Marinescu> Hi John, Thanks for the quick reply, I was really
> Marinescu> happy to download the snapshot and see that it works. I
> Marinescu> tested in on wxPython 2.5.1.5 without problems, it
> Marinescu> would probably work the same on 2.4.2.4. I'm not quite
> Marinescu> familiar with the toolbar functions, so I don't know if
> Marinescu> the results I'm getting are right. The "home" button
> Marinescu> seems to do something, I can see a visual indication of
> Marinescu> the repaint when I press it. On the other hand, the
> Marinescu> "pan" button seems to be disabled; even if I can press
> Marinescu> it, I'm unable to select it (or it isn't supposed to be
> Marinescu> selectable?) Maybe this is normal for the example that
> Marinescu> you sent in your e-mail? Because of this, I can't test
> Marinescu> the functionality of the back/forward buttons. The
> Marinescu> "zoom to rect" button also seems to be disable,
> Marinescu> probably because I didn't use the zoom function, which
> Marinescu> is also related to the "pan" button, if I understand it
> Marinescu> correctly. The "save" button worked when trying to save
> Marinescu> a PNG image, but the program exited with a "Do not know
> Marinescu> know to handle extension *.jpg" message printed on the
> Marinescu> console when trying to save a JPG image. Again, I don't
> Marinescu> know if this behavior is correct or not, I'm just
> Marinescu> posting my results.
> 
> These buttons don't do what you think they do because they all work
> very differently from the classic matplotlib toolbar (else why
> introduce a new one!)
> 
> The Forward and Back buttons are akin to the web browser forward and
> back buttons. They are used to navigate back and forth between
> previously defined views. They have no meaning unless you have
> already navigated somewhere else using the pan and zoom buttons. This
> is analogous to trying to click 'back' on your web browser before
> visiting a new page. Nothing happens. 'Home' always takes you to the
> first view. For Home, Forward and Back, think web browser where data
> views are web pages. Use the pan and zoom to rectangle to define new
> views.
> 
> The "Pan" button has two modes: pan and zoom. Click this toolbar
> button to activate this mode. Then put your mouse somewhere over an
> axes. Mode 1: Press the left mouse button and hold it, dragging it to
> a new position. When you release it, the data under the point where
> you pressed will be moved to the point where you released. Mode 2:
> Press the right mouse button, dragging it to a new position. The x
> axis will be zoomed in proportionate to the rightward movement and
> zoomed out proportionate to the leftward movement. Ditto for the
> yaxis and up/down motions.
> 
> The Zoom to rectangle button: Click this toolbar button to activate
> this mode. Put your mouse somewhere over and axes and press the left
> mouse button. Drag the mouse while holding the button to a new
> location and release. The axes view limits will be zoomed to the
> rectangle you have defined.
> 
> Save: click this button to launch a file save dialog. All the *Agg
> backends know how to save the following image types: PNG, PS, EPS,
> SVG. There is no support currently in Agg for writing to JPEG, TIFF
> (the regular wx and gtk backends handle these types). It is possible
> to use matplotlib/agg + PIL to convert agg images to one of these
> other formats if required. I can provide a recipe for you. I prefer
> PNG over JPG and TIFF, which is why I haven't worked too hard to
> include these other image formats in agg.
> 
> Marinescu> I don't plan on using the toolbar
> Marinescu> in my application, I have another (specialized) toolbar
> Marinescu> and I'll be using its functions.
> 
> OK, perhaps you could give it one more time just to make sure my
> instructions above are clear and that it is working fine on your
> system?
> 
> Marinescu> The new event handling mechanism is great and it's
> Marinescu> exactly what I needed. However, I have a couple of
> Marinescu> fresh new questions for you :) The first one was also
> Marinescu> present in my previous e-mail. When I create the plot
> Marinescu> it has very large margins to the parent frame. This is
> Marinescu> not convenient to me, as I'd like to have a plot that
> Marinescu> is as large as possible and margins as small as
> Marinescu> possible. Is there a way to modify these margins?
> 
> Yes, you can position axes anywhere you want in any size using the
> axes command. See
> http://matplotlib.sf.net/matplotlib.matlab.html#-axes and the example
> http://matplotlib.sf.net/examples/axes_demo.py.
> 
> Marinescu> The other one is really new and it is related to
> Marinescu> printing. Is there a way to print directly from the
> Marinescu> library? I'm aware of the image save/image print combo
> Marinescu> and I can use it if I have no other option. However, at
> Marinescu> this point my application (which is quite critical)
> Marinescu> blocks every task switching combination (ctrl+atl+del
> Marinescu> included, together with alt+tab and all the others) in
> Marinescu> order to force the user to use this application and
> Marinescu> ONLY this application. If I choose the "image save"
> Marinescu> option I'll be forced to give up this feature, and I
> Marinescu> don't want that, as I _KNOW_ that they'll start to play
> Marinescu> starcraft in a flash :) Unless there is some Python
> Marinescu> source somewhere that can send an image to the
> Marinescu> printer. I've been searching for it, but never found
> Marinescu> it. I also had this problem with PyPlot, that offers
> Marinescu> printing functions, but they don't seem to work :(
> Marinescu> (this was tested on two different printers). Then
> Marinescu> again, the "Print framework" sample from the wxPython
> Marinescu> 2.5.1.5 demo also crashed when trying to print, so I
> Marinescu> imagine that the printing support in wxPython is not at
> Marinescu> its best at this point :( If anybody has a solution for
> Marinescu> this, please let me know. Thank you all for your help.
> 
> cross platform printing is pretty hard, and cross-gui/cross-platform
> printing is event harder. If you get wx printing figured out and want
> to submit some code, I'd be happy to include it. When I was initially
> trying to decide on a GUI for my own application work, poor printing
> support in wx the thing that initially steered me to GTK.
> 
> JDH
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
-- 
Bogdan

>>>>> "Marinescu" == Marinescu Bogdan-bmarine1 <bog...@fr...> writes:
 Marinescu> 	Hi John, Thanks for the quick reply, I was really
 Marinescu> happy to download the snapshot and see that it works. I
 Marinescu> tested in on wxPython 2.5.1.5 without problems, it
 Marinescu> would probably work the same on 2.4.2.4. I'm not quite
 Marinescu> familiar with the toolbar functions, so I don't know if
 Marinescu> the results I'm getting are right. The "home" button
 Marinescu> seems to do something, I can see a visual indication of
 Marinescu> the repaint when I press it. On the other hand, the
 Marinescu> "pan" button seems to be disabled; even if I can press
 Marinescu> it, I'm unable to select it (or it isn't supposed to be
 Marinescu> selectable?) Maybe this is normal for the example that
 Marinescu> you sent in your e-mail? Because of this, I can't test
 Marinescu> the functionality of the back/forward buttons. The
 Marinescu> "zoom to rect" button also seems to be disable,
 Marinescu> probably because I didn't use the zoom function, which
 Marinescu> is also related to the "pan" button, if I understand it
 Marinescu> correctly. The "save" button worked when trying to save
 Marinescu> a PNG image, but the program exited with a "Do not know
 Marinescu> know to handle extension *.jpg" message printed on the
 Marinescu> console when trying to save a JPG image. Again, I don't
 Marinescu> know if this behavior is correct or not, I'm just
 Marinescu> posting my results. 
These buttons don't do what you think they do because they all work
very differently from the classic matplotlib toolbar (else why
introduce a new one!)
The Forward and Back buttons are akin to the web browser forward and
back buttons. They are used to navigate back and forth between
previously defined views. They have no meaning unless you have
already navigated somewhere else using the pan and zoom buttons. This
is analogous to trying to click 'back' on your web browser before
visiting a new page. Nothing happens. 'Home' always takes you to the
first view. For Home, Forward and Back, think web browser where data
views are web pages. Use the pan and zoom to rectangle to define new
views.
The "Pan" button has two modes: pan and zoom. Click this toolbar
button to activate this mode. Then put your mouse somewhere over an
axes. Mode 1: Press the left mouse button and hold it, dragging it to
a new position. When you release it, the data under the point where
you pressed will be moved to the point where you released. Mode 2:
Press the right mouse button, dragging it to a new position. The x
axis will be zoomed in proportionate to the rightward movement and
zoomed out proportionate to the leftward movement. Ditto for the
yaxis and up/down motions.
The Zoom to rectangle button: Click this toolbar button to activate
this mode. Put your mouse somewhere over and axes and press the left
mouse button. Drag the mouse while holding the button to a new
location and release. The axes view limits will be zoomed to the
rectangle you have defined.
Save: click this button to launch a file save dialog. All the *Agg
backends know how to save the following image types: PNG, PS, EPS,
SVG. There is no support currently in Agg for writing to JPEG, TIFF
(the regular wx and gtk backends handle these types). It is possible
to use matplotlib/agg + PIL to convert agg images to one of these
other formats if required. I can provide a recipe for you. I prefer
PNG over JPG and TIFF, which is why I haven't worked too hard to
include these other image formats in agg.
 Marinescu> I don't plan on using the toolbar
 Marinescu> in my application, I have another (specialized) toolbar
 Marinescu> and I'll be using its functions. 
OK, perhaps you could give it one more time just to make sure my
instructions above are clear and that it is working fine on your
system?
 Marinescu> The new event handling mechanism is great and it's
 Marinescu> exactly what I needed. However, I have a couple of
 Marinescu> fresh new questions for you :) The first one was also
 Marinescu> present in my previous e-mail. When I create the plot
 Marinescu> it has very large margins to the parent frame. This is
 Marinescu> not convenient to me, as I'd like to have a plot that
 Marinescu> is as large as possible and margins as small as
 Marinescu> possible. Is there a way to modify these margins? 
Yes, you can position axes anywhere you want in any size using the
axes command. See
http://matplotlib.sf.net/matplotlib.matlab.html#-axes and the example
http://matplotlib.sf.net/examples/axes_demo.py. 
 Marinescu> The other one is really new and it is related to
 Marinescu> printing. Is there a way to print directly from the
 Marinescu> library? I'm aware of the image save/image print combo
 Marinescu> and I can use it if I have no other option. However, at
 Marinescu> this point my application (which is quite critical)
 Marinescu> blocks every task switching combination (ctrl+atl+del
 Marinescu> included, together with alt+tab and all the others) in
 Marinescu> order to force the user to use this application and
 Marinescu> ONLY this application. If I choose the "image save"
 Marinescu> option I'll be forced to give up this feature, and I
 Marinescu> don't want that, as I _KNOW_ that they'll start to play
 Marinescu> starcraft in a flash :) Unless there is some Python
 Marinescu> source somewhere that can send an image to the
 Marinescu> printer. I've been searching for it, but never found
 Marinescu> it. I also had this problem with PyPlot, that offers
 Marinescu> printing functions, but they don't seem to work :(
 Marinescu> (this was tested on two different printers). Then
 Marinescu> again, the "Print framework" sample from the wxPython
 Marinescu> 2.5.1.5 demo also crashed when trying to print, so I
 Marinescu> imagine that the printing support in wxPython is not at
 Marinescu> its best at this point :( If anybody has a solution for
 Marinescu> this, please let me know. Thank you all for your help.
cross platform printing is pretty hard, and cross-gui/cross-platform
printing is event harder. If you get wx printing figured out and want
to submit some code, I'd be happy to include it. When I was initially
trying to decide on a GUI for my own application work, poor printing
support in wx the thing that initially steered me to GTK.
JDH

Thanks a lot for the fast reply and the solution! of the
problem!!!
Regards from Berlin, Michael
On 2004年7月21日 08:53:31 -0400
Paul Barrett <ba...@st...> wrote:
> Michael Oevermann wrote:
> > I am having the same problem as reported by Serge Barrel on 2004年07月16日.
> > Mathtext works fine on the GUI and e.g. PNG format, but the PS and EPS 
> > backend
> > brings out the raw LaTeX string.
> > 
> > I am using matplotlib 0.60.2 on Mac Os X 10.3.4.
> > 
> > Any ideas how to fix the problem?
> 
> Yes. Use the updated files in CVS. Or use the two attached python files.
> 
> -- Paul
> 
> -- 
> Paul Barrett, PhD Space Telescope Science Institute
> Phone: 410-338-4475 ESS/Science Software Branch
> FAX: 410-338-4767 Baltimore, MD 21218
> 

	Have you installed the freetype2 library (freetype.sourceforge.net)?
I had the same problem last night while trying to build the wxagg
backend, I had to download the library, install it and then play quite a bit
with the settings in order to make it compile. It's not in the CVS layout. 
	HTH.
	Bogdan
-----Original Message-----
From: mat...@li...
[mailto:mat...@li...]On Behalf Of Nils
Wagner
Sent: Thursday, July 22, 2004 10:17 AM
To: mat...@li...
Subject: [Matplotlib-users] build the matplotlib users guide failed
Hi all,
I am going to build the matplotlib users guide.
However
python setup.py install failed with the follwoing message
gcc -pthread -fno-strict-aliasing -DNDEBUG -D_FILE_OFFSET_BITS=64 
-DHAVE_LARGEFILE_SUPPORT -O2 -march=i586 -mcpu=i686 -fmessage-length=0 
-Wall -fPIC -IlibImaging -I/usr/include/python2.3 -c Tk/tkImaging.c -o 
build/temp.linux-i686-2.3/Tk/tkImaging.o
Tk/tkImaging.c: In function `TkImaging_Init':
Tk/tkImaging.c:198: warning: passing arg 3 of `Tcl_CreateCommand' from 
incompatible pointer type
gcc -pthread -fno-strict-aliasing -DNDEBUG -D_FILE_OFFSET_BITS=64 
-DHAVE_LARGEFILE_SUPPORT -O2 -march=i586 -mcpu=i686 -fmessage-length=0 
-Wall -fPIC -IlibImaging -I/usr/include/python2.3 -c _imagingtk.c -o 
build/temp.linux-i686-2.3/_imagingtk.o
gcc -pthread -shared build/temp.linux-i686-2.3/_imagingtk.o 
build/temp.linux-i686-2.3/Tk/tkImaging.o -LlibImaging -lImaging -ltk8.4 
-ltcl8.4 -o build/lib.linux-i686-2.3/_imagingtk.so
building '_imagingft' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -D_FILE_OFFSET_BITS=64 
-DHAVE_LARGEFILE_SUPPORT -O2 -march=i586 -mcpu=i686 -fmessage-length=0 
-Wall -fPIC -IlibImaging -I/usr/include/freetype2 
-I/usr/include/python2.3 -c _imagingft.c -o 
build/temp.linux-i686-2.3/_imagingft.o
In file included from _imagingft.c:18:
/usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' 
hasn't been included yet!"
/usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always 
use macros to include FreeType header files."
/usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:"
/usr/include/freetype2/freetype/freetype.h:23:2: #error " #include 
<ft2build.h>"
/usr/include/freetype2/freetype/freetype.h:24:2: #error " #include 
FT_FREETYPE_H"
error: command 'gcc' failed with exit status 1
Any pointer would be appreciated.
Nils
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Matplotlib-users mailing list
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Hi all,
I am going to build the matplotlib users guide.
However
python setup.py install failed with the follwoing message
gcc -pthread -fno-strict-aliasing -DNDEBUG -D_FILE_OFFSET_BITS=64 
-DHAVE_LARGEFILE_SUPPORT -O2 -march=i586 -mcpu=i686 -fmessage-length=0 
-Wall -fPIC -IlibImaging -I/usr/include/python2.3 -c Tk/tkImaging.c -o 
build/temp.linux-i686-2.3/Tk/tkImaging.o
Tk/tkImaging.c: In function `TkImaging_Init':
Tk/tkImaging.c:198: warning: passing arg 3 of `Tcl_CreateCommand' from 
incompatible pointer type
gcc -pthread -fno-strict-aliasing -DNDEBUG -D_FILE_OFFSET_BITS=64 
-DHAVE_LARGEFILE_SUPPORT -O2 -march=i586 -mcpu=i686 -fmessage-length=0 
-Wall -fPIC -IlibImaging -I/usr/include/python2.3 -c _imagingtk.c -o 
build/temp.linux-i686-2.3/_imagingtk.o
gcc -pthread -shared build/temp.linux-i686-2.3/_imagingtk.o 
build/temp.linux-i686-2.3/Tk/tkImaging.o -LlibImaging -lImaging -ltk8.4 
-ltcl8.4 -o build/lib.linux-i686-2.3/_imagingtk.so
building '_imagingft' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -D_FILE_OFFSET_BITS=64 
-DHAVE_LARGEFILE_SUPPORT -O2 -march=i586 -mcpu=i686 -fmessage-length=0 
-Wall -fPIC -IlibImaging -I/usr/include/freetype2 
-I/usr/include/python2.3 -c _imagingft.c -o 
build/temp.linux-i686-2.3/_imagingft.o
In file included from _imagingft.c:18:
/usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' 
hasn't been included yet!"
/usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always 
use macros to include FreeType header files."
/usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:"
/usr/include/freetype2/freetype/freetype.h:23:2: #error " #include 
<ft2build.h>"
/usr/include/freetype2/freetype/freetype.h:24:2: #error " #include 
FT_FREETYPE_H"
error: command 'gcc' failed with exit status 1
Any pointer would be appreciated.
Nils

	Hi John,
	Thanks for the quick reply, I was really happy to download 
the snapshot and see that it works. I tested in on wxPython 2.5.1.5 
without problems, it would probably work the same on 2.4.2.4. I'm
not quite familiar with the toolbar functions, so I don't know if 
the results I'm getting are right. The "home" button seems to do
something, I can see a visual indication of the repaint when I
press it. On the other hand, the "pan" button seems to be disabled;
even if I can press it, I'm unable to select it (or it isn't
supposed to be selectable?) Maybe this is normal for the example 
that you sent in your e-mail? Because of this, I can't test the
functionality of the back/forward buttons. The "zoom to rect" button
also seems to be disable, probably because I didn't use the zoom
function, which is also related to the "pan" button, if I understand
it correctly. The "save" button worked when trying to save a PNG image,
but the program exited with a "Do not know know to handle extension *.jpg"
message printed on the console when trying to save a JPG image. Again,
I don't know if this behavior is correct or not, I'm just posting
my results. I don't plan on using the toolbar in my application, I have
another (specialized) toolbar and I'll be using its functions.
	The new event handling mechanism is great and it's exactly what
I needed. However, I have a couple of fresh new questions for you :)
	The first one was also present in my previous e-mail. When I create
the 
plot it has very large margins to the parent frame. This is not convenient
to 
me, as I'd like to have a plot that is as large as possible and margins 
as small as possible. Is there a way to modify these margins?
	The other one is really new and it is related to printing. Is there
a way to print directly from the library? I'm aware of the image save/image
print combo and I can use it if I have no other option. However, at this
point my application (which is quite critical) blocks every task switching
combination (ctrl+atl+del included, together with alt+tab and all the
others)
in order to force the user to use this application and ONLY this 
application. If I choose the "image save" option I'll be forced to give
up this feature, and I don't want that, as I _KNOW_ that they'll start to
play starcraft in a flash :) Unless there is some Python source somewhere
that can send an image to the printer. I've been searching for it, but 
never found it. I also had this problem with PyPlot, that offers 
printing functions, but they don't seem to work :( (this was tested on
two different printers). Then again, the "Print framework" sample
from the wxPython 2.5.1.5 demo also crashed when trying to print,
so I imagine that the printing support in wxPython is not at its
best at this point :( If anybody has a solution for this, please let
me know.
	Thank you all for your help.
	Bogdan
>>>>> "Bogdan" == Bogdan Marinescu <bogdanal@b.astral.ro> writes:
 Bogdan> Hello all, First I want to apologize for sending this
 Bogdan> message to both lists, but I couldn't decide which one is
 Bogdan> more appropriate and I would like to have an answer as
 Bogdan> soon as possible. 
Hi Bogdan, 
Either list is appropriate for this kind of post. I think the users
is slightly better because then other users who may have seen the
error will get the benefit of the post and response. cross-posting
will not speed up the response, but may delay it :-)
 Bogdan> I discovered matplotlib some while ago, but it wasn't
 Bogdan> until recently when I decided to integrate it into one of
 Bogdan> my programs, trying to replace PyPlot that doesn't have
 Bogdan> enough features for me. I downloaded and installed version
 Bogdan> 0.60.2. Your library seemed perfect, until I discovered
 Bogdan> some strange problems that prevented me from using it as
 Bogdan> this point :( Specifically, I'm reffering to the
 Bogdan> embedding_in_wx2.py example that I found in the 'examples'
 Bogdan> directory. I modified it as follows (sorry for inlining,
 Bogdan> but I don't know if the listserver accepts any
 Bogdan> attachements at all, I didn't use it before):
Thanks for your example. I was able to trace the segfault (exposed on
win32 but not linux in my tests) to agg.tostring_rgb, as you noted.
On window maximizing, there was an uncaught memory allocation error
because I was allocating on the stack rather than the heap. This is
fixed, and your (modified) example now runs fine for me on win32.
I've built a snapshot of matplotlib-0.61 for you and uploaded it to
 
http://nitace.bsd.uchicago.edu:8080/files/share/matplotlib-0.61.0a.win32-py2
.3.exe
You'll notice a few changes: a new navigation toolbar - see
http://sourceforge.net/mailarchive/forum.php?thread_id=5173059&forum_id=3618
7
for a discussion of the new icons, what they do, and how to get the
old toolbar if you want it. As before, you can also just comment out
the set_toolbar line to remove the toolbar completely.
Also, the event handling mechanism has been changed as part of the
process of making this more generic and useful. You now call
mpl_connect rather than connect and your callback takes a single
argument. For example, if you want to know where the user clicks a
mouse on your figure, you define a function
def click(event):
 print 'you clicked', event.x, event.y
and register this function with the event handler
canvas.mpl_connect('button_press_event', click) 
Then whenever the user clicks anywhere on the figure canvas, your
function will be called and passed a
matplotlib.backend_bases.MplEvent instance. The event instance has
the following attributes defined.
 name # the event name
 canvas # the FigureCanvas instance generating the event
 x # x position - pixels from left of canvas
 y # y position - pixels from bottom of canvas
 button # button pressed None, 1, 2, 3
 inaxes # the Axes instance if mouse us over axes
 xdata # x coord of mouse in data coords
 ydata # y coord of mouse in data coords
You can currently connect to the following events:
'button_press_event', button_release_event', 'motion_notify_event' and
I plan to add key press.
Below is your example, modified to work with 0.61. I fixed the event
handling and took out the onpaint connection from init (this did some
funky things in my win32 tests)
Let me know how it goes: you're the first 0.61 crash test dummy.
Anyone else who wants to try this please feel free - the new toolbar
only works with GTK* and WX* in this snapshot.
#!/usr/bin/env python
"""
An example of how to use wx or wxagg in an application w. or w/o the toolbar
"""
import matplotlib
matplotlib.use('WXAgg')
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as
FigureCanvas
from matplotlib.backends.backend_wx import NavigationToolbar2Wx
from matplotlib.figure import Figure
from matplotlib.numerix import arange, sin, pi
from wxPython.wx import *
class Cursor:
 def __init__(self, canvas, ax):
 self.canvas = canvas
 self.ax = ax
 def mouse_move(self, event):
 x, y = event.x, event.y
 if event.inaxes:
 ax = event.inaxes
 minx, maxx = ax.get_xlim()
 miny, maxy = ax.get_ylim()
 print 'x=%1.2f, y=%1.2f'%(event.xdata, event.ydata)
class CanvasFrame(wxFrame):
 def __init__(self):
 wxFrame.__init__(self,None,-1,
 'CanvasFrame',size=( 900,900 ) )
 self.SetBackgroundColour(wxNamedColor("WHITE"))
 self.figure = Figure( )
 self.axes = self.figure.add_subplot(111)
 t = arange(0.0,3.0,0.01)
 s = sin(2*pi*t)
 c = sin(4*pi*t)
 p = self.axes.fill(t,s,'b',t,c,'g')
 p[ 0 ].set_alpha( 0.2 )
 p[ 1 ].set_alpha( 0.2 )
 #p = self.axes.fill(t,s,'b')
 #p[ 0 ].set_alpha( 0.2 )
 #p[ 1 ].set_alpha( 0.2 )
 #self.axes.plot(t,c,'g')
 self.axes.vlines( [1.5], -1.0, 1.0 )
 self.canvas = FigureCanvas(self, -1, self.figure)
 self.sizer = wxBoxSizer(wxVERTICAL)
 self.sizer.Add(self.canvas, 1, wxTOP | wxLEFT | wxEXPAND)
 self.SetSizer(self.sizer)
 self.SetAutoLayout( True )
 self.sizer.Fit( self )
 
 cursor = Cursor(self.canvas, self.axes)
 #cursor = SnaptoCursor(canvas, ax, t, s)
 self.canvas.mpl_connect('motion_notify_event', cursor.mouse_move)
 self.add_toolbar() # comment this out for no toolbar
 # Capture the paint message
 #EVT_PAINT(self, self.OnPaint)
 EVT_SIZE( self, self.OnSize)
 def add_toolbar(self):
 self.toolbar = NavigationToolbar2Wx(self.canvas)
 self.toolbar.Realize()
 if wxPlatform == '__WXMAC__':
 # Mac platform (OSX 10.3, MacPython) does not seem to cope with
 # having a toolbar in a sizer. This work-around gets the buttons
 # back, but at the expense of having the toolbar at the top
 self.SetToolBar(self.toolbar)
 else:
 # On Windows platform, default window size is incorrect, so set
 # toolbar width to figure width.
 tw, th = self.toolbar.GetSizeTuple()
 fw, fh = self.canvas.GetSizeTuple()
 # By adding toolbar in sizer, we are able to put it at the
bottom
 # of the frame - so appearance is closer to GTK version.
 # As noted above, doesn't work for Mac.
 self.toolbar.SetSize(wxSize(fw, th))
 self.sizer.Add(self.toolbar, 0, wxLEFT | wxEXPAND)
 # update the axes menu on the toolbar
 self.toolbar.update()
 def OnSize( self, event ):
 print "OnSize"
 print event.GetSize()
 event.Skip()
# event.Skip()
class App(wxApp):
 def OnInit(self):
 'Create the main window and insert the custom frame'
 frame = CanvasFrame()
 frame.Show(true)
 return true
app = App(0)
app.MainLoop()