Skip to content

Refactor: simplify mouse movement implementation for Windows, use set… #711

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

Merged
merged 1 commit into from
Mar 8, 2025

Conversation

vcaesar
Copy link
Member

@vcaesar vcaesar commented Mar 8, 2025

Please provide Issues links to:

Provide test code:

    

Description

...

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@vcaesar vcaesar added this to the v1.0.0 milestone Mar 8, 2025
@vcaesar vcaesar merged commit 0343215 into master Mar 8, 2025
2 of 6 checks passed
@PekingSpades
Copy link

Using the new Windows API to simulate mouse movements causes the system interface to fail to respond to mouse drag events.
To reproduce it: drag the app squares in the Windows 10 menu (with the aim of changing their position).
Using the SetCursorPos function invalidates the drag. the SendInput function does not cause this issue.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants