-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Avoid 1-tick or 0-tick log-scaled axis. #12865
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
26ce31c
to
c5b9ce4
Compare
This looks like the axes have become linear?!? |
They haven't, but on such a small range they'll look linear (#8768 (comment)). |
+lots for this, but definitely an API change so should get a note! |
done |
putting on the backport queue, though not strictly necessary... |
Woops. API change note is not there. Did you forget to push? |
... by switching to AutoLocator when the minor LogLocator would produce no more than one tick.
c5b9ce4
to
a918a13
Compare
Indeed, it got lost on the way. Fixed. |
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon! If these instruction are inaccurate, feel free to suggest an improvement. |
@jklymak You labelled as 3.0.3. Any interest in backporting? I would be fine with just leaving it in 3.1 as it's not a regression. |
... by switching to AutoLocator when the minor LogLocator would produce
no more than one tick.
The examples below come from #8768, which this fixes.
PR Summary
PR Checklist