Crosshair is not positioned correctly when one of the
axes is not locked to data. In this case it is snapped
to the "closest to zero" value on the other axis.
From the implementation standpoint, it is caused by
the way updateCrosshairX/Y methods in CrosshairState
class are called.
The supplied patch resolves the problem and also fixes
crosshair painting and positioning for ContourPlot.
Log in to post a comment.