Deprecate dpi_cor property of FancyArrowPatch. #17751
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
We always reset this property to a renderer-dependent value in draw(), so user-set values have no effect and this property is basically just a way for draw() to communicate renderer dpi to the arrow transmuters. So deprecate it, and replace it for now by the corresponding private attribute (but see comment).
|
yup |
timhoffm
approved these changes
Jun 25, 2020
QuLogic
approved these changes
Jun 25, 2020
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.
We always reset this property to a renderer-dependent value in draw(),
so user-set values have no effect and this property is basically just a
way for draw() to communicate renderer dpi to the arrow transmuters. So
deprecate it, and replace it for now by the corresponding private
attribute (but see comment).
PR Summary
PR Checklist