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
In general, using event.inaxes/event.xdata/event.ydata can be
error-prone when there are overlapping axes, because only the topmost
axes is the "in"-axes.
In the specific case of widgets, in particular, we can instead check
whether an event occurred over the axes and if so compute xdata/ydata
accordingly. Doing so allows correct handling of widgets on axes for
which there's also a twin axes on top of it.
Changes in the tests (other than the change in test_span_selector, which
tests the functionality here) ensure that the synthetic button presses
indeed occur on top of the desired axes (previously, do_event would
directly set event.inaxes and we'd just believe that "as is").
0 commit comments