matplotlib-users Mailing List for matplotlib

>>>>> "Brent" == Brent Hueth <bh...@ia...> writes:
 Brent> This is a problem for me only b/c I'm trying to generate a
 Brent> plot with a total number of subplots > 10.
 Brent> I can't seem to track down the source of the discrepancy.
 Brent> Thanks,
This is a bug in 0.82 that is fixed in CVS and will be fixed in the
next bugfix release.
The patch that fixed it is
http://sourceforge.net/tracker/index.php?func=detail&aid=1222180&group_id=80706&atid=560722
JDH

Hello,
Is this a bug, or am I missing something:
 
>>> from pylab import *
>>> s = subplot(211)
>>> s._num
0
>>> s = subplot(212)
>>> s._num
1
>>> t = subplot(2,1,1)
>>> t._num
0
>>> t = subplot(2,1,2)
>>> t._num
0
This is a problem for me only b/c I'm trying to generate a plot with a total
number of subplots > 10.
I can't seem to track down the source of the discrepancy. 
Thanks,
Brent

On 2005年6月28日, Jeff Whitaker wrote:
> John: OK, I've fixed it so pylab is not imported at all if either (1) the 
> 'ax' keyword is used in Basemap.__init__ (in which case only one axes 
> instance is used by that Basemap instance), or (2) the 'ax' keyword is used 
> in all Basemap method calls that do drawing (in which case different axes may 
> be used by the same Basemap instance). If you don't use the 'ax' keyword, 
> basemap methods behave like their pylab counterparts (i.e. pylab.gca is used 
> to get the current axis).
Great! That's perfect for us. Thanks for the quick response.
We have exactly the setup that John was describing. We use Basemap in 
cron jobs that don't have any X windows support. Our default backend is 
Qt, and Qt itself aborts and core dumps (!) if you try to use it when 
there's no X server present. So we wanted to avoid pylab loading a 
backend.
I guess we'll see these changes in the next release, 0.5.2 or 0.6, 
whichever is next, yes?
Thanks again,
Michael
========================================================================
 Michael Brady
 Jet Propulsion Laboratory (M/S 301-140L)
 4800 Oak Grove Drive
 Pasadena, CA 91109 E-mail: Mic...@jp... 
========================================================================

Jeff Whitaker wrote:
> John: OK, I've fixed it so pylab is not imported at all if either (1) 
> the 'ax' keyword is used in Basemap.__init__ (in which case only one 
> axes instance is used by that Basemap instance), or (2) the 'ax' keyword 
> is used in all Basemap method calls that do drawing (in which case 
> different axes may be used by the same Basemap instance). If you don't 
> use the 'ax' keyword, basemap methods behave like their pylab 
> counterparts (i.e. pylab.gca is used to get the current axis).
Nice job Jeff. You've come up with a solution that satisfies a wide 
variety of uses. Hurray for keyword arguments!
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

Hi Werner, 
This should be tested on Mac and Linux too. I had portability
problems when I originally wrote the printing support. I can
believe that wx has gotten better.
But also, the current Printer_Setup() provides a simple way to
control the size of the image on the paper. I didn't see that on
yours.
--Matt
On 2005年6月28日, Werner F. Bruhin wrote:
> Hi John,
> 
> The attached backend_wx contains "def Printer_Setup2(self, 
> event=None):", which uses the standard wxPython printer setup dialog 
> this works for me on Windows XP Pro SP1, and Windows 2000.
> 
> Any chance that this could go into the next release?
> 
> See you
> Werner
> 

John Hunter wrote:
>>>>>>"Jeff" == Jeff Whitaker <js...@fa...> writes:
>>>>>> 
>>>>>>
>
> Jeff> Michael: By popular demand, I put this back in 0.5.1. You
> Jeff> can now pass an axes instance to any Basemap method. The
> Jeff> default is 'ax=None', in which case pylab.gca is used to get
> Jeff> the current one. Does this solve your problem?
>
>You can potentially get into trouble by simply importing the pylab
>module at all since pylab will try and import the default backend.
>This usually isn't fatal, but isn't ideal either. I would suggest
>conditionally importing pylab only if it is needed, eg when ax=None.
>
>The use case you would be avoiding is for example when the user hasn't
>changed the default backend (GTKAgg) from .matplotlibrc. They may be
>using non-pylab basemap in pure agg mode over a web app server. When
>you import pylab, the module will try and import pygtk, which will
>fail if pygtk is not installed or if there is no X11 connection. Of
>course, the user could change the default backend in the rc file, but
>one point of the OO interface is to have as little magic as possible.
>By conditionally importing pylab, you can avoid these kinds of
>problems.
>
>JDH 
> 
>
John: OK, I've fixed it so pylab is not imported at all if either (1) 
the 'ax' keyword is used in Basemap.__init__ (in which case only one 
axes instance is used by that Basemap instance), or (2) the 'ax' keyword 
is used in all Basemap method calls that do drawing (in which case 
different axes may be used by the same Basemap instance). If you don't 
use the 'ax' keyword, basemap methods behave like their pylab 
counterparts (i.e. pylab.gca is used to get the current axis).
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/CDC1 FAX : (303)497-6449
325 Broadway Web : http://www.cdc.noaa.gov/~jsw
Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124

Hi John,
The attached backend_wx contains "def Printer_Setup2(self, 
event=None):", which uses the standard wxPython printer setup dialog 
this works for me on Windows XP Pro SP1, and Windows 2000.
Any chance that this could go into the next release?
See you
Werner

On Monday 27 June 2005 16:22, John Hunter wrote:
> >>>>> "Jesper" == Jesper Larsen <jl...@dm...> writes:
>
> Jesper> Dear matplotlib-users, I have made an application for
> Jesper> tsunami wave travel time prediction (slowmo.sf.net). The
> Jesper> application uses the basemap toolkit and is developed on
> Jesper> Linux. I would like to offer potential Windows users an
> Jesper> easier way to install and test it than is currently
> Jesper> available.
>
> Jesper> For this I would need a binary windows package of the
> Jesper> basemap toolkit in a newer version than 0.21 which is
> Jesper> currently available. Unfortunately I do not have access to
> Jesper> the windows compilers that are necessary to make this
> Jesper> binary package. I would therefore be very grateful if
> Jesper> anyone from this list has the binary or could easily
> Jesper> produce it.
>
> OK, I just uploaded win32 binaries for basemap 0.5.1 for python2.3 and
> 2.4. Give them and test drive and let us know if there are any
> problems.
>
> JDH
Thanks John,
I only tested the binaries for Python2.3. They seem to work fine.
Jesper