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
Bug summary
The multicursor widget does not check if the events it receives are in the axes it received in init. So mouse move events on any axis in the figure will cause the cursor to move.
I guess it's actually a little bit unclear what the intended behavior is. I could see an argument that the reason you are providing the axes is just to denote which axes get a line drawn on them, but without a docstring (#19634) it's hard to say. Though my expectation is definitely that the only axes that should matter are the ones that get passed to init.
Activity
ianhi commentedon Mar 4, 2021
The fix here is to change:
matplotlib/lib/matplotlib/widgets.py
Lines 1653 to 1657 in bac91f5
to have the second
ifstatement read:ianhi commentedon Mar 4, 2021
I guess it's actually a little bit unclear what the intended behavior is. I could see an argument that the reason you are providing the
axesis just to denote which axes get a line drawn on them, but without a docstring (#19634) it's hard to say. Though my expectation is definitely that the only axes that should matter are the ones that get passed toinit.