Repository navigation
Confusing status bar values in presence of multiple axes #5506
Description
Run
plt.plot([1, 2]); plt.twinx().plot([4, 3])
The xy values printed in the status bar are those of the twin axes (I guess because they were added last), which is somwhat confusing. I'd suggest listing the coordinates in all overlaid axes systems instead.
Activity
tacaswell commented on Nov 18, 2015
Also see discussion at #2986
The limitation is how the event handling system deals with over-lapping axes (which is to give the event to the top one and be done with it).
anntzer commented on Nov 18, 2015
Perhaps we should just reopen the old issue and close this one?
kawing-chiu commented on Jan 19, 2016
Is there a workaround for this at the moment? In my case, I have
and I want the y=<...> in the status bar to show ax1's y value instead of ax1t's.
WeatherGod commented on Jan 19, 2016
Unfortunately, I don't think there is a workaround, except to flip around
which axes twins which, which probably isn't ideal.
On Tue, Jan 19, 2016 at 1:06 AM, kawing-chiu notifications@github.com
wrote:
tacaswell commented on Jan 19, 2016
See https://stackoverflow.com/questions/16672530/cursor-tracking-using-matplotlib-and-twinx/16672970#16672970 for a start on how to do this.
github-actions commented on Mar 19, 2023
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
anntzer commented on Mar 21, 2023
Displaying the coordinates on all axes over which the mouse cursor is (#2986 (comment)) still seems reasonable to me.
github-actions commented on Mar 22, 2024
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!