Fixed missing scaling for MouseWheel events on Windows#20
Open
emuell wants to merge 1 commit into
Open
Conversation
... and log or trace errors from `ScreenToClient` and co as warnings
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
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.
Also, the
PhysicalToLogicalPointhack was missing for MouseWheel event. I guess that the same applies here, but I can't test that, because PhysicalToLogicalPoint and co don't do anything on my Windows setups.Further, errors from
ScreenToClientgot handled with anassert!for MouseWheel events, but got silently ignored in the drag and drop impl. I've unified both, too, and do log them now. I think a warning is fine here, a panic would be too much, but that's your call to make.NB: This is a regression of: dd350f8