dynamic ticking (#5588) should avoid (if possible) single ticks #5784
Comments
|
This also starts to touch on the need for categorical axis support. |
|
I think this is also partially addressed by #5772 |
|
This is still a problem http://matplotlib.org/devdocs/examples/statistics/violinplot_demo.html
|
|
I think that improving this without practically defeating the 'auto' functionality requires a combination of setting a lower bound for the upper bound value, as in #6470, combined with letting the Locator switch to a larger set of "nice" intervals from which to choose. The larger the set of intervals, the easier it is to fit in a target number of ticks. The problem is that unless this larger set is exposed as yet another kwarg and rcParam, it will lead to surprises--the Locator will do something other than what the user thought she told it to do, with no way to override that behavior. In other words, it adds another layer of complexity. |
This requires falling back on a larger set of options for intervals between ticks. Closes matplotlib#5784.
This requires falling back on a larger set of options for intervals between ticks. Closes matplotlib#5784.
|
With #6584: |
There's only one xtick left in
statistics/violinplot_demo.pyafter #5588 got merged:Compare with before the patch:
The old xticks were perhaps a bit cramped but there's clearly room for, say, two more xticks in the new output.
(On the other hand, this helped me catch a bug in offset text calculation logic when there's a single tick, so it's not all that bad...)
The text was updated successfully, but these errors were encountered: