On 07/21/2010 05:26 PM, John Hunter wrote:
On Wed, Jul 21, 2010 at 10:09 PM, Tony S Yutsy...@gmail.com wrote:
Wow, I don't see that at all. I'm on OS X, mpl svn HEAD (r8567), and Qt4Agg.
I don't have GTK installed, so unfortunately, I can't really do a proper
comparison. Here's the output I
On Wed, Jul 21, 2010 at 3:38 AM, Andrew Straw straw...@astraw.com wrote:
We could also make a meta repository that uses git submodules (somewhat akin
to svn externals).
I have to confess that I first heard of git submodules when you first
mentioned them on this list a while ago, but a
On 07/21/2010 05:26 PM, John Hunter wrote:
On Wed, Jul 21, 2010 at 10:09 PM, Tony S Yutsy...@gmail.com wrote:
Wow, I don't see that at all. I'm on OS X, mpl svn HEAD (r8567), and Qt4Agg.
I don't have GTK installed, so unfortunately, I can't really do a proper
comparison. Here's the output I
--- On Wed, 7/21/10, Tony S Yu tsy...@gmail.com wrote:
I get something similar with TkAgg (unfortunately, I get an
AttributeError with the macosx backend).
This is the AttributeError:
Traceback (most recent call last):
File Desktop/tight_layout.py, line 142, in module
tight_layout()
On Thu, Jul 22, 2010 at 7:40 AM, Michiel de Hoon mjldeh...@yahoo.com wrote:
Is a backend required to implement a get_renderer method? I only see it
implemented in backend_agg.py, and it's missing in backend_bases.py,
backend_template.py, backend_cairo.py, and in the macosx backend. If you
On Jul 22, 2010, at 8:59 AM, John Hunter wrote:
On Thu, Jul 22, 2010 at 7:40 AM, Michiel de Hoon mjldeh...@yahoo.com wrote:
Is a backend required to implement a get_renderer method? I only see it
implemented in backend_agg.py, and it's missing in backend_bases.py,
backend_template.py,
On Thu, Jul 22, 2010 at 8:57 AM, Tony S Yu tsyu80@
According to backend_bases.FigureCanvas, a renderer attr is not
guaranteed either.
The Agg* backends rely on get_renderer so that they can get a properly
sized renderer on figure resizes, dpi changes, etc. We could handle
this on the agg
--- On Thu, 7/22/10, John Hunter jdh2...@gmail.com wrote:
We could handle this on the agg side with a property,
or require all canvases to supply get renderer.
Do we actually need a renderer in each of the backends? At least when I was
writing the Mac OS X backend, it was not clear to me what
On Jul 22, 2010, at 10:07 AM, John Hunter wrote:
On Thu, Jul 22, 2010 at 8:57 AM, Tony S Yu tsyu80@
According to backend_bases.FigureCanvas, a renderer attr is not
guaranteed either.
The Agg* backends rely on get_renderer so that they can get a properly
sized renderer on figure resizes,
On Mon, Jul 19, 2010 at 10:13 AM, Ryan May rma...@gmail.com wrote:
On Sun, Jul 18, 2010 at 6:16 PM, Benjamin Root ben.r...@ou.edu wrote:
A few corrections. First, I wrong, it is unusual. The second axes that
I
noticed in a 2d case came from a colorbar being added. Second, in the 3d
Heh, looks more pervasive than just the Tkinter backend, and it isn't just
caused by zooming. Just moving the image off to the side is enough, and
saving that figure using the Save button produces this attached image.
And further testing shows that this occurs if I manually set my limits
before
On 07/22/2010 04:34 PM, Benjamin Root wrote:
Heh, looks more pervasive than just the Tkinter backend, and it isn't
just caused by zooming. Just moving the image off to the side is
enough, and saving that figure using the Save button produces this
attached image.
And further testing shows
On Thu, Jul 22, 2010 at 9:46 PM, Eric Firing efir...@hawaii.edu wrote:
On 07/22/2010 04:34 PM, Benjamin Root wrote:
Heh, looks more pervasive than just the Tkinter backend, and it isn't
just caused by zooming. Just moving the image off to the side is
enough, and saving that figure using
13 matches
Mail list logo
