Fix: Use SendInput({ MOUSEINPUT { ... } }) for simulating mouse movement. #90
Conversation
This file contains 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
* Use SendInput() based mouse cursor positioning during mouse movements (replaces SetCursorPos based positioning) * Remove mouse cursor parameters in click events (they were ignored in SendInput() due to missing MOUSEEVENTF_MOVE flag)
leexgone
approved these changes
Dec 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix: Use SendInput({ MOUSEINPUT { ... } }) for simulating mouse movement
Background:
We found that using SetCursorPos for setting the mouse position during mouse movement can lead to unexpected issues. For example, the Windows 'Start Button' context menu (right click on the 'Start Button') will not accept the first mouse click if the mouse was positioned using SetCursorPos.