Remove buggy on_monitor method and handle scrolling #127
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
on_monitor() does not work well with two monitors. If the parent window is moved by x, the tooltip gets moved by 2x. Handling scrolling is necessary to avoid the tool tip gettings stuck in the showing state when the widget loses hot status due to scrolling and not mouse move.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I hit a few bugs while using tooltips, workarounds below.
on_monitor() does not work well with two monitors on windows 10. If the parent window is moved by x, the tooltip gets moved by 2x.
Handling scrolling is necessary to avoid the tool tip getting stuck in the showing state when the widget loses hot status due to scrolling and not MouseMove.