Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
FIX: make MaxNLocator only follow visible ticks for order of magnitude#12086
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Seems to have broken some docs when there are no visible ticks. |
Ha, it passes all of |
fc00626
toed1c830
CompareModulo the docs... |
@anntzer I think the docs are OK (they say it'll just key off the data, not the data plus one tick on either side). It does need tests, which I'll do now. I actually don't understand why |
Added test that fails master but passes this PR... |
3183f78
to9a23d6d
CompareThanks@jklymak ! |
PR Summary
Closes#12072
Order of magnitude for tick formatting in ScalarFormatter was using invisible ticks. This changes to just use visible.
Probably obviated by#11004 but won't hurt anything.
Before:
After
Code
PR Checklist