You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The real reason is that axes_pad<>0 will affect the same picture every time it's rendered (to be saved or displayed), and change its dimensions by 2% each time by default. I can understand the need for axes_pad, but don't think this should happen:
pdehayemannequin
changed the title
graphics_array messes up dimensions of plots
rendering a plot changes its dimensions [was: graphics_array messes up dimensions of plots]
Jan 21, 2010
I think the problem is that in the save routine (actually, in the .matplotlib() method), the x and y limits are changed according to the axes_pad setting. Instead, they should be temporarily changed and then changed back so that the graphic has the same x and y limits as it did when starting.
The following code should illustrate this, see picture below, everything gets scaled for no reason.
The real reason is that axes_pad<>0 will affect the same picture every time it's rendered (to be saved or displayed), and change its dimensions by 2% each time by default. I can understand the need for axes_pad, but don't think this should happen:
and compare with
Component: graphics
Keywords: axes_range, axes_pad
Author: Paul Dehaye
Issue created by migration from https://trac.sagemath.org/ticket/8019
The text was updated successfully, but these errors were encountered: