DOC: Fix annotation position (issue #7345) #7346
Merged
Conversation
This file contains hidden or 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
phobson
changed the title
NelleV
added a commit
that referenced
this pull request
Oct 25, 2016
DOC: Fix annotation position (issue #7345)
Member
|
backported in v2.x as 0030e7a |
Member
|
Thanks @afvincent ! |
QuLogic
changed the title
QuLogic
modified the milestones:
2.0.1 (next bug fix release),
2.0 (style change major release)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Here is a proposition of PR to fix #7345 . I tried to avoid the use of data coords along the x-axis. The current results is :
For the record, initially I was simply planning to pass a blended transformation to
ax.text, with a negative x coordinate in Axes coords, but somehow it did not work as I was expecting. So I switched toax.annotate, with an "offset point" approach…