matplotlib-devel Mailing List for matplotlib

John,
Is there anything special required to get the subplot configuration tool 
available from QtAgg? I'm in the process of fixing that sizing problem 
reported last week and the only way to fix it was to change how the toolbar 
layout works so I'm mucking around in the toolbar right now.
I guess I'll sync and take a look at the Gtk backend and see what happens 
in there...
Ted
At 01:14 PM 6/15/2005, John Hunter wrote:
>What's new in 0.82
>
>Subplot configuration
>
> All of the parameters of the subplots are now exposed at the rc,
> pylab and API layout. These are left, right, bottom, top, wspace
> and hspace which control how the subplots are placed on the screen.
> See figure.SubplotParams, figure.Figure.subplots_adjust and the
> pylab method subplots_adjust and examples/subplots_adjust.py . Also
> added a GUI neutral widget for adjusting subplots, see
> examples/subplot_toolbar.py. There is a new toolbar button on GTK*,
> WX* and TkAgg to launch the subplot configuration tool (which uses
> the new matplotlib cross GUI classes discussed below).
>
> This also makes it easier to make ganged plots -- see
> examples/ganged_plots.py
>
> Note this required a small change to how the toolbar on some GUIs
> are imported; if you are using the mpl API in WXAgg and GTKAgg, see
> API_CHANGES.
>
>GUI neutral widgets
>
> Matplotlib now has cross-GUI widgets (buttons, check buttons, radio
> buttons and sliders). You have to manually create properly sized
> Axes for them to live in, but otherwise they are pretty easy to use.
> See examples/widgets/*.py and
> http://matplotlib.sf.net/screenshots.html#slider_demo. This makes
> it easier to create interactive figures that run across backends.
>
>Cap and join style
>
> Exposes line cap and join style via new rc params and Line2D
> properties
>
> lines.dash_joinstyle : miter # miter|round|bevel
> lines.dash_capstyle : butt # butt|round|projecting
> lines.solid_joinstyle : miter # miter|round|bevel
> lines.solid_capstyle : projecting # butt|round|projecting
>
>Axes kwargs
>
> All Axes properties are now exposed via kwargs, so you can do, for
> example
>
> subplot(111, xlabel='time', ylabel='volts', autoscale_on=False,
> xlim=(-1,1), ylim =(0,10) )
>
>Small bugfixes and features:
>
> Fixed a upper/right tick bug (thanks Baptiste), fixed invalid rc
> docstring vis-a-vis aliases, fixed bug #1217637 in ticker.py and a
> cleanup bug in usetex (thanks Darren), added Sean Richards hist bin
> fix (see API_CHANGES)
>
>http://matplotlib.sf.net
>
>Enjoy!
>JDH
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Matplotlib-devel mailing list
>Mat...@li...
>https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Ted Drain Jet Propulsion Laboratory ted...@jp... 

John Hunter wrote:
>>>>>>"Steve" == Steve Chaplin <ste...@ya...> writes:
> 
> 
> Steve> Figure.get_width_height() returns width, height as floats,
> Steve> but isn't width, height of a Figure always integers, and
> Steve> wouldn't it make sense to return these as integers?
> 
> Steve> This would enable changing the code: width, height =
> Steve> figure.get_width_height() width, height = int(width),
> Steve> int(height)
> 
> Steve> to simply: width, height = figure.get_width_height()
> 
> The width and height of a figure are width/height in inches * dpi, and
> both dpi and the width/height vars can be floats. So no, these values
> don't have to be integers. In the postscript backend, for example, it
> returns the width and height of the figure in points. We could add a
> convenience kwarg to the method, since in practice it is usually used
> by GUI developers who want the dimensions in pixels
> 
> w, h = fig.get_width_height(asinteger=True)
> 
> If you think this is a good idea, feel free to add it.
Just to be nitpicky, isn't this a bit of API bloat, when a simple
w, h = map(int,fig.get_width_height())
does the job just fine? And it's even less characters :)
Cheers,
f

What's new in 0.82
Subplot configuration
 All of the parameters of the subplots are now exposed at the rc,
 pylab and API layout. These are left, right, bottom, top, wspace
 and hspace which control how the subplots are placed on the screen.
 See figure.SubplotParams, figure.Figure.subplots_adjust and the
 pylab method subplots_adjust and examples/subplots_adjust.py . Also
 added a GUI neutral widget for adjusting subplots, see
 examples/subplot_toolbar.py. There is a new toolbar button on GTK*,
 WX* and TkAgg to launch the subplot configuration tool (which uses
 the new matplotlib cross GUI classes discussed below). 
 This also makes it easier to make ganged plots -- see
 examples/ganged_plots.py
 Note this required a small change to how the toolbar on some GUIs
 are imported; if you are using the mpl API in WXAgg and GTKAgg, see
 API_CHANGES.
GUI neutral widgets
 Matplotlib now has cross-GUI widgets (buttons, check buttons, radio
 buttons and sliders). You have to manually create properly sized
 Axes for them to live in, but otherwise they are pretty easy to use.
 See examples/widgets/*.py and
 http://matplotlib.sf.net/screenshots.html#slider_demo. This makes
 it easier to create interactive figures that run across backends.
Cap and join style
 Exposes line cap and join style via new rc params and Line2D
 properties
 lines.dash_joinstyle : miter # miter|round|bevel
 lines.dash_capstyle : butt # butt|round|projecting
 lines.solid_joinstyle : miter # miter|round|bevel
 lines.solid_capstyle : projecting # butt|round|projecting
Axes kwargs
 All Axes properties are now exposed via kwargs, so you can do, for
 example
 subplot(111, xlabel='time', ylabel='volts', autoscale_on=False,
 xlim=(-1,1), ylim =(0,10) )
Small bugfixes and features:
 Fixed a upper/right tick bug (thanks Baptiste), fixed invalid rc
 docstring vis-a-vis aliases, fixed bug #1217637 in ticker.py and a
 cleanup bug in usetex (thanks Darren), added Sean Richards hist bin
 fix (see API_CHANGES)
http://matplotlib.sf.net
Enjoy!
JDH

>>>>> "Steve" == Steve Chaplin <ste...@ya...> writes:
 Steve> Figure.get_width_height() returns width, height as floats,
 Steve> but isn't width, height of a Figure always integers, and
 Steve> wouldn't it make sense to return these as integers?
 Steve> This would enable changing the code: width, height =
 Steve> figure.get_width_height() width, height = int(width),
 Steve> int(height)
 Steve> to simply: width, height = figure.get_width_height()
The width and height of a figure are width/height in inches * dpi, and
both dpi and the width/height vars can be floats. So no, these values
don't have to be integers. In the postscript backend, for example, it
returns the width and height of the figure in points. We could add a
convenience kwarg to the method, since in practice it is usually used
by GUI developers who want the dimensions in pixels
 w, h = fig.get_width_height(asinteger=True)
If you think this is a good idea, feel free to add it.
JDH

Figure.get_width_height() returns width, height as floats,
but isn't width, height of a Figure always integers, and wouldn't it
make sense to return these as integers?
This would enable changing the code:
 width, height = figure.get_width_height()
 width, height = int(width), int(height)
to simply:
 width, height = figure.get_width_height()
Steve
Send instant messages to your online friends http://au.messenger.yahoo.com