Re: [matplotlib-devel] figimages

2008-06-22 Thread John Hunter
On Thu, Jun 19, 2008 at 5:46 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> I believe there is a bug in the figimage handling when multiple images
> are present.  It looks like there is a negative sign in the
> transformation that shouldn't be there.  It is common to get upside
> down in mpl, since bottom is 0 for us and usually bottom is top

Well, it almost killed me but I finally figured out the cause of this
bug: the origin rc param was being ignored for composite images.  I
fixed in r5618 this for fig and axes images.

JDH

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] upcoming release

2008-06-22 Thread Eric Firing
John Hunter wrote:
> Sandro has been working hard packaging matplotlib 0.98.0 for debian
> ahead of the next major debian feature freeze, and says he can get
> 0.98.1 in if we release it by June 24th.  Charlie, can you do a
> release on Monday?  All developers, please take some time to fix any
> bugs you are aware of and let's release 0.91.4 and 0.98.1 on Monday
> pending Charlie's availability.  These major debian releases only
> happen once every couple of years so we want to get good versions in.
> 
> JDH

It is probably too late for this upcoming release, but I would like to 
raise a relevant question for discussion:

Can and should we rearrange the code, or install warnings and 
documentation, to make it absolutely clear what is supported and what is 
not?  Ideally, if someone installs 0.98.x from any distribution, or from 
the tarball, the user should be able to expect *everything* to work, 
including all backends, examples, and plotting-related classes.

The simplest way to deal with this would be to leave everything where it 
is, if there is any hope that it will ever be fixed and maintained, but 
to put a warnings.warn and a docstring comment in any module or example 
that does not currently work.  That way, if someone imports axes3d, they 
would (or at least might, unless it goes by too fast) see the warning 
and know that if they want it to work, they will simply have to take on 
its maintenance.

A second step would be to have one or more separate subdirectories to 
separate the maintained from the unmaintained.  Doing this in a nice, 
consistent, easy-to-use way would take a little more work.  For example, 
one would want to make it very easy for someone to restore a backend 
from broken and segregated to fully operational and available.

Eric

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] bug: axes limits being reset

2008-06-22 Thread Andrew Straw
Hi,

I've encountered behavior in the svn trunk that I think is a bug.
Namely, the axes view limits are reset to the data limits upon a UI
event callback. In the attached test script for example, the plot
initially displays with the correct view limits (between -10 and 10 on
the X axis). However, when a key is pressed, the view is automatically
(and falsely) reset to encompass the entire data limits. I believe this
behavior has changed since 0.91.

Thanks,
Andrew
import pylab
import numpy

class ShowIt:
def on_key_press(self,event):
print 'received key',repr(event.key)
for ax in [self.ax1,self.ax2]:
xlim = ax.get_xlim()
ylim = ax.get_ylim()
ax.plot([0,0],'kx')
print 'set xlim',xlim
print 'set ylim',ylim
ax.set_xlim(xlim)
ax.set_ylim(ylim)
xlim = ax.get_xlim()
ylim = ax.get_ylim()
print 'got xlim',xlim
print 'got ylim',ylim
print
pylab.draw()

def show_it(self,fig):
ax1 = fig.add_subplot(2,1,1)
x1 = numpy.linspace(-100,100,100)
y1 = numpy.sin( x1/30.0 )
ax1.plot(x1,y1,'o')
xlim = [-10,10]
ylim = [-1,1]
ax2 = fig.add_subplot(2,1,2)
x2 = numpy.linspace(-100,100,100)
y2 = numpy.sin( x1/30.0 )
ax2.plot(x2,y2,'o')
ax2.set_xlim([-10,10])
ax2.set_ylim([-1,1])

self.ax1 = ax1
self.ax2 = ax2

for ax in [ax1,ax2]:
print 'set xlim',xlim
print 'set ylim',ylim
ax.set_xlim(xlim)
ax.set_ylim(ylim)
xlim = ax.get_xlim()
ylim = ax.get_ylim()
print 'got xlim',xlim
print 'got ylim',ylim
print

fig.canvas.mpl_connect('key_press_event', self.on_key_press)

fig = pylab.figure()

showit = ShowIt()
showit.show_it(fig)
pylab.show()
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Inheritance graphs

2008-06-22 Thread Fernando Perez
Hey Michael,

On Fri, Jun 20, 2008 at 7:47 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> John Hunter wrote:
>> On Fri, Jun 20, 2008 at 8:13 AM, Michael Droettboom <[EMAIL PROTECTED]> 
>> wrote:
>>
>>
>>> The current version of graphviz uses either cairo or gd (the default being
>>> cairo on most modern installations.)
>>>
>>
>>
>>> Now that you've uploaded the docs, I see that the font you're getting isn't
>>> as nice as mine.  I was setting "fontname" to "sans", which is supposed to
>>> get the default sans serif font on the system.  It appears, from testing,
>>> one can provide a list of fonts to dot, so I'll change it to try good fonts
>>> first, with sans as the last resort fallback.
>>>
>>
>> I'm building and uploading the docs in a nightly cron on a linux box
>> that Fernando maintains.  Can you tell him what package(s) need to be
>> installed to insure cairo rendering so he can update the box?
> My understanding is that gd doesn't support antialiasing at all, so if
> you're seeing antialiasing you're using Cairo.  To be absolutely certain
> you're using Cairo, you can change the "-Tpng" to "-Tpng:cairo" (though
> I don't know if we should do that in general, since it will break for
> users who don't have Cairo, if such users exist...).
>
> With my latest updates, you should ensure that there is a decent-looking
> font, such as Vera Sans, on the fontconfig path.  You should also make
> sure that libpango is being used by your graphviz.  It's optional in
> graphviz, but is used by the pre-built packages on Debian Etch and
> Ubuntu Hardy at least.

Unfortunately this is a Fedora 8 box that was given to me.  I do have
sudo access, so I can install whatever we want, but it's not ubuntu.
I may update it to Ubuntu later (that's what I use on all my regular
machines) but right now I'm too busy for that.

Do you have any clue as to what packages might do the trick for
Fedora?  I'm happy to add anything, I just don't know what to look
for...

Cheers,

f

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Inheritance graphs

2008-06-22 Thread Michael Droettboom
Fernando Perez wrote:
> Hey Michael,
>
> On Fri, Jun 20, 2008 at 7:47 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
>   
>> John Hunter wrote:
>> 
>>> On Fri, Jun 20, 2008 at 8:13 AM, Michael Droettboom <[EMAIL PROTECTED]> 
>>> wrote:
>>>
>>>
>>>   
 The current version of graphviz uses either cairo or gd (the default being
 cairo on most modern installations.)

 
>>>   
 Now that you've uploaded the docs, I see that the font you're getting isn't
 as nice as mine.  I was setting "fontname" to "sans", which is supposed to
 get the default sans serif font on the system.  It appears, from testing,
 one can provide a list of fonts to dot, so I'll change it to try good fonts
 first, with sans as the last resort fallback.

 
>>> I'm building and uploading the docs in a nightly cron on a linux box
>>> that Fernando maintains.  Can you tell him what package(s) need to be
>>> installed to insure cairo rendering so he can update the box?
>>>   
>> My understanding is that gd doesn't support antialiasing at all, so if
>> you're seeing antialiasing you're using Cairo.  To be absolutely certain
>> you're using Cairo, you can change the "-Tpng" to "-Tpng:cairo" (though
>> I don't know if we should do that in general, since it will break for
>> users who don't have Cairo, if such users exist...).
>>
>> With my latest updates, you should ensure that there is a decent-looking
>> font, such as Vera Sans, on the fontconfig path.  You should also make
>> sure that libpango is being used by your graphviz.  It's optional in
>> graphviz, but is used by the pre-built packages on Debian Etch and
>> Ubuntu Hardy at least.
>> 
>
> Unfortunately this is a Fedora 8 box that was given to me.  I do have
> sudo access, so I can install whatever we want, but it's not ubuntu.
> I may update it to Ubuntu later (that's what I use on all my regular
> machines) but right now I'm too busy for that.
>   
I didn't mean to imply that Debian/Ubuntu was required, those are just 
the ones that I looked at as a sampling.  It looks like Fedora 8 also 
links graphviz with libpango, according to its rpm spec.
> Do you have any clue as to what packages might do the trick for
> Fedora?  I'm happy to add anything, I just don't know what to look
> for...
>   
It looks like you're already good to go, judging by what's now up on 
matplotlib.sf.net.  My change this morning to use "Vera Sans", if 
available, rather than "sans" (which maps to the default sans-serif font 
on the system), seems to have done the trick.

The issues John pointed out -- the fuzzy rectangles, bad arrowhead 
alignment -- seem to just be what graphviz does.  We're not going to get 
any better without being clever.

Cheers,
Mike

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] matplotlib-0.98 Failure to Build

2008-06-22 Thread Eric Firing
It is trying to build the gdk extension but you don't have the devel 
package installed, so it can't find the headers.  What puzzles me is 
that it *knows* it can't find the headers, so it shouldn't be trying to 
build the extension.  Are you using a setup.cfg file?  (Ordinarily, one 
should not.)

Eric

B Clowers wrote:
> After downloading the source and following the instructions, I've been 
> unable to build matplotlib on Ubuntu Hardy.  Any ideas?
> 
> BUILDING MATPLOTLIB
> matplotlib: 0.98.0
> python: 2.5.2 (r252:60911, Apr 21 2008, 11:12:42)  [GCC
> 4.2.3 (Ubuntu 4.2.3-2ubuntu7)]
>   platform: linux2
> 
> REQUIRED DEPENDENCIES
>  numpy: 1.1.0
>  freetype2: 9.16.3
> 
> OPTIONAL BACKEND DEPENDENCIES
> libpng: 1.2.15beta5
>Tkinter: no
> * Using default library and include directories for
> * Tcl and Tk because a Tk window failed to open.
> * You may need to define DISPLAY for Tk to work so
> * that setup can determine where your libraries are
> * located. Tkinter present, but header files are not
> * found. You may need to install development
> * packages.
>   wxPython: 2.8.7.1
> * WxAgg extension not required for wxPython >= 2.8
>   Gtk+: gtk+: 2.12.9, glib: 2.16.3, pygtk: 2.12.1,
> pygobject: 2.14.1
> * Could not find Gtk+ headers in any of
> * '/usr/local/include', '/usr/include', '.'
> Qt: no
>Qt4: no
>  Cairo: 1.4.0
> 
> OPTIONAL DATE/TIMEZONE DEPENDENCIES
>   datetime: present, version unknown
>   dateutil: 1.3
>   pytz: 2007k
> 
> OPTIONAL USETEX DEPENDENCIES
> dvipng: 1.9
>ghostscript: 8.61
>  latex: 3.141592
>pdftops: 3.00
> 
> EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES
>  configobj: 4.4.0
>   enthought.traits: 2.0.1b1
> 
> [Edit setup.cfg to suppress the above messages]
> 
> running build
> running build_py
> copying lib/matplotlib/mpl-data/matplotlibrc -> 
> build/lib.linux-i686-2.5/matplotlib/mpl-data
> copying lib/matplotlib/mpl-data/matplotlib.conf -> 
> build/lib.linux-i686-2.5/matplotlib/mpl-data
> running build_ext
> building 'matplotlib.backends._backend_gdk' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fPIC 
> -I/usr/lib/python2.5/site-packages/numpy-1.1.0-py2.5-linux-i686.egg/numpy/core/include
>  
> -I/usr/local/include -I/usr/include -I. -I/usr/local/include 
> -I/usr/include -I. -I/usr/include/python2.5 -c src/backend_gdk.c -o 
> build/temp.linux-i686-2.5/src/backend_gdk.o
> src/backend_gdk.c:9:25: error: pygtk/pygtk.h: No such file or directory
> src/backend_gdk.c: In function ‘pixbuf_get_pixels_array’:
> src/backend_gdk.c:28: error: ‘PyGObject’ undeclared (first use in this 
> function)
> src/backend_gdk.c:28: error: (Each undeclared identifier is reported 
> only once
> src/backend_gdk.c:28: error: for each function it appears in.)
> src/backend_gdk.c:28: error: ‘py_pixbuf’ undeclared (first use in this 
> function)
> src/backend_gdk.c:29: error: ‘GdkPixbuf’ undeclared (first use in this 
> function)
> src/backend_gdk.c:29: error: ‘gdk_pixbuf’ undeclared (first use in this 
> function)
> src/backend_gdk.c:37: warning: implicit declaration of function ‘GDK_PIXBUF’
> src/backend_gdk.c:43: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_height’
> src/backend_gdk.c:44: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_width’
> src/backend_gdk.c:45: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_has_alpha’
> src/backend_gdk.c:48: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_pixels’
> src/backend_gdk.c:53: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_rowstride’
> src/backend_gdk.c: In function ‘init_backend_gdk’:
> src/backend_gdk.c:72: warning: implicit declaration of function ‘init_pygtk’
> error: command 'gcc' failed with exit status 1
> 
> 
> 
> 
> 
> 
> -
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> 
> 
> 
> 
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.ne

Re: [matplotlib-devel] upcoming release

2008-06-22 Thread Darren Dale
On Friday 20 June 2008 13:32:46 Eric Firing wrote:
> John Hunter wrote:
> > Sandro has been working hard packaging matplotlib 0.98.0 for debian
> > ahead of the next major debian feature freeze, and says he can get
> > 0.98.1 in if we release it by June 24th.  Charlie, can you do a
> > release on Monday?  All developers, please take some time to fix any
> > bugs you are aware of and let's release 0.91.4 and 0.98.1 on Monday
> > pending Charlie's availability.  These major debian releases only
> > happen once every couple of years so we want to get good versions in.
> >
> > JDH
>
> It is probably too late for this upcoming release, but I would like to
> raise a relevant question for discussion:
>
> Can and should we rearrange the code, or install warnings and
> documentation, to make it absolutely clear what is supported and what is
> not?  Ideally, if someone installs 0.98.x from any distribution, or from
> the tarball, the user should be able to expect *everything* to work,
> including all backends, examples, and plotting-related classes.
>
> The simplest way to deal with this would be to leave everything where it
> is, if there is any hope that it will ever be fixed and maintained, but
> to put a warnings.warn and a docstring comment in any module or example
> that does not currently work.  That way, if someone imports axes3d, they
> would (or at least might, unless it goes by too fast) see the warning
> and know that if they want it to work, they will simply have to take on
> its maintenance.
>
> A second step would be to have one or more separate subdirectories to
> separate the maintained from the unmaintained.  Doing this in a nice,
> consistent, easy-to-use way would take a little more work.  For example,
> one would want to make it very easy for someone to restore a backend
> from broken and segregated to fully operational and available.

I think we should do warnings, documentation, and consider removing 
unmaintained code like axes3d. We talked a while back about adding separately 
distributable toolkits for unmaintained and license-incompatible projects. 
Maybe we could revisit that idea.

Darren

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] matplotlib-0.98 Failure to Build

2008-06-22 Thread B Clowers
Yes, it is weird as I don't have gdk installed.  I wasn't using a config file 
but now that you mention it if I do use a config file it will compile correctly.

Thanks

Brian

--- On Sat, 6/21/08, Eric Firing <[EMAIL PROTECTED]> wrote:
From: Eric Firing <[EMAIL PROTECTED]>
Subject: Re: [matplotlib-devel] matplotlib-0.98 Failure to Build
To: [EMAIL PROTECTED]
Cc: matplotlib-devel@lists.sourceforge.net
Date: Saturday, June 21, 2008, 8:46 PM

It is trying to build the gdk extension but you don't have the devel 
package installed, so it can't find the headers.  What puzzles me is 
that it *knows* it can't find the headers, so it shouldn't be trying to

build the extension.  Are you using a setup.cfg file?  (Ordinarily, one 
should not.)

Eric

B Clowers wrote:
> After downloading the source and following the instructions, I've been

> unable to build matplotlib on Ubuntu Hardy.  Any ideas?
> 
> BUILDING MATPLOTLIB
> matplotlib: 0.98.0
> python: 2.5.2 (r252:60911, Apr 21 2008, 11:12:42)  [GCC
> 4.2.3 (Ubuntu 4.2.3-2ubuntu7)]
>   platform: linux2
> 
> REQUIRED DEPENDENCIES
>  numpy: 1.1.0
>  freetype2: 9.16.3
> 
> OPTIONAL BACKEND DEPENDENCIES
> libpng: 1.2.15beta5
>Tkinter: no
> * Using default library and include directories
for
> * Tcl and Tk because a Tk window failed to open.
> * You may need to define DISPLAY for Tk to work so
> * that setup can determine where your libraries
are
> * located. Tkinter present, but header files are
not
> * found. You may need to install development
> * packages.
>   wxPython: 2.8.7.1
> * WxAgg extension not required for wxPython >=
2.8
>   Gtk+: gtk+: 2.12.9, glib: 2.16.3, pygtk: 2.12.1,
> pygobject: 2.14.1
> * Could not find Gtk+ headers in any of
> * '/usr/local/include',
'/usr/include', '.'
> Qt: no
>Qt4: no
>  Cairo: 1.4.0
> 
> OPTIONAL DATE/TIMEZONE DEPENDENCIES
>   datetime: present, version unknown
>   dateutil: 1.3
>   pytz: 2007k
> 
> OPTIONAL USETEX DEPENDENCIES
> dvipng: 1.9
>ghostscript: 8.61
>  latex: 3.141592
>pdftops: 3.00
> 
> EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES
>  configobj: 4.4.0
>   enthought.traits: 2.0.1b1
> 
> [Edit setup.cfg to suppress the above messages]
>

> running build
> running build_py
> copying lib/matplotlib/mpl-data/matplotlibrc -> 
> build/lib.linux-i686-2.5/matplotlib/mpl-data
> copying lib/matplotlib/mpl-data/matplotlib.conf -> 
> build/lib.linux-i686-2.5/matplotlib/mpl-data
> running build_ext
> building 'matplotlib.backends._backend_gdk' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fPIC 
>
-I/usr/lib/python2.5/site-packages/numpy-1.1.0-py2.5-linux-i686.egg/numpy/core/include

> -I/usr/local/include -I/usr/include -I. -I/usr/local/include 
> -I/usr/include -I. -I/usr/include/python2.5 -c src/backend_gdk.c -o 
> build/temp.linux-i686-2.5/src/backend_gdk.o
> src/backend_gdk.c:9:25: error: pygtk/pygtk.h: No such file or directory
> src/backend_gdk.c: In function ‘pixbuf_get_pixels_array’:
> src/backend_gdk.c:28: error: ‘PyGObject’ undeclared (first use in this

> function)
> src/backend_gdk.c:28: error: (Each undeclared identifier is reported 
> only once
> src/backend_gdk.c:28: error: for each function it appears in.)
> src/backend_gdk.c:28: error: ‘py_pixbuf’ undeclared (first use in this

> function)
> src/backend_gdk.c:29: error: ‘GdkPixbuf’ undeclared (first use in this

> function)
> src/backend_gdk.c:29: error: ‘gdk_pixbuf’ undeclared (first use in
this 
> function)
> src/backend_gdk.c:37: warning: implicit declaration of function
‘GDK_PIXBUF’
> src/backend_gdk.c:43: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_height’
> src/backend_gdk.c:44: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_width’
> src/backend_gdk.c:45: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_has_alpha’
> src/backend_gdk.c:48: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_pixels’
> src/backend_gdk.c:53: warning: implicit declaration of function 
> ‘gdk_pixbuf_get_rowstride’
> src/backend_gdk.c: In function ‘init_backend_gdk’:
> src/backend_gdk.c:72: warning: implicit declaration of function
‘init_pygtk’
> error: command 'gcc' failed with exit status 1
> 
> 
> 
> 
> 
> 
> 

[matplotlib-devel] Error in backend_qt4.py v0.98

2008-06-22 Thread B Clowers


p, li { white-space: pre-wrap; }

I have a small program that displays a embeds a figure along with the 
navigation toolbar into a PyQt4 application.  In version 0.91 it works fine, 
however, I get the following error when I try to run the program with 0.98 .  
An exception is raised at line 296 of the backend_qt4.py .  I've attached the 
output from Eric4.  Is there something I can do to my program or is this a more 
fundamental issue?ThanksBrian--ps this issue only seems to be a problem if I'm 
using the navigation toolbar, a regular plot is ok.
The debugged program raised the exception unhandled AttributeError
"coordinates"
File: /usr/lib/python2.5/site-packages/matplotlib/backends/backend_qt4.py, 
Line: 296StdErr: QLayout: Attempting to add QLayout "" to MyNavigationToolbar 
"", which already has a layout



  -
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Error in backend_qt4.py v0.98

2008-06-22 Thread Darren Dale
Hi Brian,

On Sunday 22 June 2008 11:01:36 B Clowers wrote:
> p, li { white-space: pre-wrap; }
>
> I have a small program that displays a embeds a figure along with the
> navigation toolbar into a PyQt4 application.  In version 0.91 it works
> fine, however, I get the following error when I try to run the program with
> 0.98 .  An exception is raised at line 296 of the backend_qt4.py .  I've
> attached the output from Eric4.  Is there something I can do to my program
> or is this a more fundamental issue?ThanksBrian--ps this issue only seems
> to be a problem if I'm using the navigation toolbar, a regular plot is ok.
> The debugged program raised the exception unhandled AttributeError
> "coordinates"
> File: /usr/lib/python2.5/site-packages/matplotlib/backends/backend_qt4.py,
> Line: 296StdErr: QLayout: Attempting to add QLayout "" to
> MyNavigationToolbar "", which already has a layout

Version 98 changed the backend_qt4 toolbar so it is a true Qt toolbar, which 
already has a layout. I guess you need to use the existing layout, rather than 
adding a new one.

If that doesn't help you, please post a *short* standalone script that 
reproduces the problem. Its hard to diagnose these things based on so little 
information.

Darren

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] upcoming release

2008-06-22 Thread John Hunter
On Fri, Jun 20, 2008 at 10:20 AM, Charlie Moad <[EMAIL PROTECTED]> wrote:
> Can we shoot for Sunday night?  It would be much more convenient for me at
> least.

I'll be traveling most of the day so I will be mostly out of
touch(some blackberry access), but I did a round of testing on the
branch and the trunk and things look good to go from my end.

JDH

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] upcoming release

2008-06-22 Thread Charles Moad
The releases and builds are up.  Please test them out, and I'll leave  
the announcements to you, John.


- Charlie

On Jun 22, 2008, at 12:43 PM, John Hunter wrote:

On Fri, Jun 20, 2008 at 10:20 AM, Charlie Moad <[EMAIL PROTECTED]>  
wrote:
Can we shoot for Sunday night?  It would be much more convenient  
for me at

least.


I'll be traveling most of the day so I will be mostly out of
touch(some blackberry access), but I did a round of testing on the
branch and the trunk and things look good to go from my end.

JDH


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel