You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is scoped to 2D type = date axes when there is no ticktext.
We need to add a new attribute (proposed name ticklabelmode) whose default value (instant) describes the current behaviour of our axes.
The new behaviour (period) would cause the tick label (not the tick or gridline!) to be positioned at the midpoint of the period that its current formatting represents (note: this means that it's sensitive to tickformat and tickformatstops). So for example if the ticklabel is Jan then instead of positioning it at YYYY-01-01 00:00 (the 'instant') we would position it at YYYY-01-15 12:00 (the midpoint of the 'period').
The text was updated successfully, but these errors were encountered:
When setting nticks=14 and ticklabelmode="period", the labels should be directly between the ticks: 50% right-shifted. However, when setting nticks=5 and ticklabelmode="period" the labels should be about 25% right-shifted, so as to be placed in the middle of the period that the label represents.
This issue is scoped to 2D
type = date
axes when there is noticktext
.We need to add a new attribute (proposed name
ticklabelmode
) whose default value (instant
) describes the current behaviour of our axes.The new behaviour (
period
) would cause the tick label (not the tick or gridline!) to be positioned at the midpoint of the period that its current formatting represents (note: this means that it's sensitive totickformat
andtickformatstops
). So for example if the ticklabel isJan
then instead of positioning it atYYYY-01-01 00:00
(the 'instant') we would position it atYYYY-01-15 12:00
(the midpoint of the 'period').The text was updated successfully, but these errors were encountered: