-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Prevent tooltips from overlapping buttons in NavigationToolbar2Tk (fixes issue mentioned in #22028) #22078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change itself is fine.
Please do not merge the main branch into a PR. As far as I understand git that will cause problems when we backport this for 3.5.2, which would be the natural thing to do for this bugfix. If you need to take changes from main into account in your branch here, please rebase on main.
67b504d
to
5b4701a
Compare
This is not technically true. The backport uses the merge commit vs the previous However, we do prefer rebases over merges, especially for small singular commit PRs like this one. |
5b4701a
to
6629ce6
Compare
The failing test looks unrelated to the change |
codecov sometimes does strange things. TBH I don't understand it either. |
I restarted the failing test, it isn't failing any more; codecov is correct, we don't test tooltips. |
…ns in NavigationToolbar2Tk (fixes issue mentioned in matplotlib#22028)
PR Summary
As mentioned in the comments of #22028, the tooltips for the navigation toolbar buttons in the Tk backend overlap the right side of the buttons (probably DPI/resolution dependent), as the x-offset is hardcoded. This makes the right half of the buttons unresponsive, as the tooltip is continuously being shown and hidden. This PR always makes the tooltip appear directly to the right of its button.
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).