Updated CHANGELOG and whats_new.rst: with (re-)generate auto-legend #3047
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -226,6 +226,10 @@ added. Furthermore, the the subplottool is now implemented as a modal | |||
| dialog. It was previously a QMainWindow, leaving the SPT open if one closed the | |||
| plotwindow. | |||
|
|
|||
| In the figureoptions dialog one can now choose to (re-)generate a simple | |||
| automatic legend. Any fancyness of a customized legend will be lost. But changes | |||
There was a problem hiding this comment.
'fancyness' is not a word. Change to 'Any explicitly set legend entries will be lost, but..'
Updated whats_new.rst: Wording of figureoptions doc
|
I merged 2 of the 3 commits in this PR by hand (dropped the merge commit). Closing this PR as the relevant commits are currently on master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
in Qt4Agg backend.
As requested in #2947 (comment)
(Fix of Issue #2934)