On Thu, Jul 22, 2010 at 9:46 PM, Eric Firing 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 the "Save" bu
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 s
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 Mon, Jul 19, 2010 at 10:13 AM, Ryan May wrote:
> On Sun, Jul 18, 2010 at 6:16 PM, Benjamin Root 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
> > case, it was the Axes3DSubp
On Jul 22, 2010, at 10:07 AM, John Hunter wrote:
> On Thu, Jul 22, 2010 at 8:57 AM, Tony S Yu
>>> 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 resize
--- On Thu, 7/22/10, John Hunter 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 functionality
On Thu, Jul 22, 2010 at 8:57 AM, Tony S Yu > 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 sid
On Jul 22, 2010, at 8:59 AM, John Hunter wrote:
> On Thu, Jul 22, 2010 at 7:40 AM, Michiel de Hoon 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.
On Thu, Jul 22, 2010 at 7:40 AM, Michiel de Hoon 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 want
> to try your
--- On Wed, 7/21/10, Tony S Yu 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
tight_layout()
File "Desktop/tight_l
10 matches
Mail list logo
