GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — AxisArtist to use standard tick directions and have an option for tick orientation by leejjoon · Pull Request #24553 · matplotlib/matplotlib Conversation
Contributor
PR SummaryThis is a rebased version of PR #19102 that addresses issue #19101. It also add an option to change the orientation of ticks. The ticks in AxisArtist were drawn along the gridlines and may not be perpendicular to spines. This PR introduce an option of
PR ChecklistDocumentation and Tests
Release Notes
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsi.e. defaulting to "out". Also support "inout". Would perpendicular work better for "out"? see e.g. demo_curvelinear_grid.
oscargus
reviewed
| |||||||||||||||||||||||||||||||||||||||||||||
| # If ticklabels and axislabel are on differenct side, we only | ||
| # conside the padding for the ticks only. | ||
|
|
||
| ticksizes = [] |
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Can you add a test that uses this path? (And ideally "all" the newly introduced options.)
Edit: one way to at least test the out/in/inout combinations would be to regenerate some of the test images below.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Yes, I will do.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| @image_comparison(['curvelinear3.png'], style='default', tol=5) | ||
| def test_curvelinear3(): | ||
| # Remove this lines when this test image is regenerated. | ||
| plt.rcParams.update({"xtick.direction": "in", "ytick.direction": "in"}) |
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
If I get it correct, this changes the current behavior? Not sure if we should introduce some way to make that transition smoothly, but at least a change note would be in place, I guess.
(Edit: this comment holds for the whole change, not just this line.)
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
When we went to v2 we changed ticks from in to out, however because AxisArtist did not follow the rcparams they did not flip when everything else did.
I do not think there is a way to soften this change short of adding another rcparam.
I think we should go forward with this, but make sure there is a very clear API change note.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I have added a deprecation warning at the level of Tick creation and relevant tests. On the other hand, users won't see the warning unless they manually create a Tick instance. I briefly thought about adding a tickdir keyword argument for Axes initialization, but not very inclined for now. I agree with @tacaswell that it is better to go with it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| @@ -62,7 +62,7 @@ | |||
|
|
|||
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
The line above (which I cannot mark...) should be updated as well?
Currently:
ax.axis["bottom"].major_ticks.set_tick_out(True)
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Since this Pull Request has not been updated in 60 days, it has been marked "inactive." This does not mean that it will be closed, though it may be moved to a "Draft" state. This helps maintainers prioritize their reviewing efforts. You can pick the PR back up anytime - please ping us if you need a review or guidance to move the PR forward! If you do not plan on continuing the work, please let us know so that we can either find someone to take the PR over, or close it. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
#19102 was rebased as #30369, so tick direction should now be available. However, if an option for tick orientation is still desired, this PR can still be used. I have not reviewed the conflicts however, so I don't know how easy that is to untangle. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
At least 1 approving review is required to merge this pull request.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.