Re: [matplotlib-devel] API change in transforms branch

[Jeff W. <js...@fa...>]

Michael Droettboom wrote:
> It may be now be tricky to call apply_aspect correctly.  With the 
> recent auto-layout changes, it's required to be called after the text 
> layout has been done, but before it has been drawn.  What is your use 
> case for calling it outside of that?  Do you need to set and then use 
> the aspect-adjusted axes position?  Since apply_aspect is always 
> called from within draw() anyway, for most uses, calling outside of 
> that would be redundant, and I was considering making it a private 
> method.  If you don't call it from your code, is anything different?
>
> Cheers,
> Mi

Mike:  The only side effect of not calling apply_aspect that I can see 
involves the use of ax.get_position().  The axes position that you get 
is not what will ultimately be drawn on the figure unless you call 
apply_aspect before get_position.  This comes into play when setting the 
position of colorbar axes, since you want them to line up with the axes 
of the image.

-Jeff
>
> Jeff Whitaker wrote:
>>
>> Mike: I see that ax.apply_aspect now has a 'position' argument.  To 
>> maintain backward compatibility, may I suggest that you make it a 
>> kwarg, with default value None, and then add
>>
>> if position is None:
>>    position = self._originalPosition
>>
>> at the top of apply_aspect?
>>
>> -Jeff
>>
>


-- 
Jeffrey S. Whitaker         Phone : (303)497-6313
NOAA/OAR/CDC  R/PSD1        FAX   : (303)497-6449
325 Broadway                Boulder, CO, USA 80305-3328