Skip to content

Conversation

dmcdougall
Copy link
Member

Fixes #1262.

Note, once the position is set, it can't be changed on a new call to suptitle. I think it might be a better idea to allow the user to change the position on subsequent calls to suptitle.

@dmcdougall
Copy link
Member Author

Do we want a test for this? If not, this is good to go.

@efiring
Copy link
Member

efiring commented Nov 5, 2012

Do we want the kwargs to be ignored on subsequent calls, as they will be in the present state of this PR?

@dmcdougall
Copy link
Member Author

Eyes like a hawk. I will fix that. Thanks.

@dmcdougall
Copy link
Member Author

I think that's better.

@dmcdougall dmcdougall mentioned this pull request Jan 15, 2013
@dmcdougall
Copy link
Member Author

Since this is a bugfix, I opened a new pull request that targets v1.2.x. See #1663.

@dmcdougall dmcdougall closed this Jan 15, 2013
@pelson
Copy link
Member

pelson commented Jan 16, 2013

Since this is a bugfix

Ah the old gray line.... 😄 - one could equally argue that you are extending previously designed behaviour and therefore this is an enhancement 😉.

Either way, as I've made clear before, I really hope it makes no difference and we can get on and get a v1.3 release (which IMHO is already feature packed) out.

@dmcdougall
Copy link
Member Author

That's a fair point. In my opinion, the design before this change appears to overlook the issue of it not being overwritten on an update. In any case, mention of its behaviour in the docstring, at a minimum, should go into v1.2.1.

Though, as you've said, it probably makes no difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using figure.suptitle puts another suptitle on top of any existing one.
3 participants