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, > Mike
Mike: Perhaps I am just misusing it - I thought you had to call it for the set_aspect to take effect. I didn't realize it was called from draw(). I'll try removing it and re-run all the basemap examples to see if there are any side effects. -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 ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
