Repository navigation
dynamic ticking (#5588) should avoid (if possible) single ticks #5784
Description
There's only one xtick left in statistics/violinplot_demo.py after #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...)
Activity
tacaswell commentedon Jan 2, 2016
This also starts to touch on the need for categorical axis support.
tacaswell commentedon Jan 3, 2016
I think this is also partially addressed by #5772
tacaswell commentedon May 23, 2016
This is still a problem
http://matplotlib.org/devdocs/examples/statistics/violinplot_demo.html
efiring commentedon May 28, 2016
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.
FIX: try hard to ensure at least 2 ticks with 'auto'
FIX: try hard to ensure at least 2 ticks with 'auto'
FIX: try to ensure 2 ticks with AutoLocator.
FIX: try to ensure 2 ticks with AutoLocator.
efiring commentedon Jun 15, 2016
With #6584:
