From: Todd <tod...@gm...> - 2013-02-08 10:21:38
|
On Fri, Feb 8, 2013 at 3:38 AM, Jason Grout <jas...@cr...>wrote: > On 2/7/13 8:08 PM, Erik Bray wrote: > > A couple easier solutions: Allow > > the `.title` (and other such attributes) to be assigned to with a > > (value, options) tuple where the value is the title itself, and the > > options is a dictionary or tuple of supported options for the title. > > Interesting. Just brainstorming here...then > > ax.title += (None, moreoptions) > > could set more options (without changing the title text or already set > options), or > > ax.title -= (None, deleteoptions) > > could reset just certain options to default values. > > Thanks, > > Jason > I am not a fan of this approach. It seems to be trying to force a property to behave like a function when it isn't meant to behave like a function. In my mind a property is just that, a single aspect of an object. If you want to change another aspect, you need to change another property. So these "moreoptions" need to have their own properties, either in the axes object or, better yet, since they are properties of the title text, have them as properties of a text object. |