-
Notifications
You must be signed in to change notification settings - Fork 43
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
Correct the order of MouseUp and MouseDown #33
base: master
Are you sure you want to change the base?
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.
But this changed break other mouse event, and can't listening MouseDown before drag too.
Sorry I am not following, what does break? (can you give an example) |
You can click mouse, and the mouse down and up is not right. |
which os? for me it works with the PR changes on Windows 11 |
Mac os. And the PR should be tested before merge. |
Well I just tested on Max OS and same, it only works the way I need for my patch Try: https://github.com/ldemailly/gohook_sample/blob/main/mouseIssue.go note that the issue is the missing mouse Up, if you click and hold; the end (release) should be MouseUp and with your original code it's MouseDown This being said with my patch it's both with your original code: click and hold, then release:
(ie my issue #32) with your original code: quick tap/click: (without holding/dragging):
with my change: (with the replace in go.mod) click and hold; then release:
which is what I need/expect but yes quick tap:
the down event is unreliable as it's missing anyway when holding but release should be |
If you have a better fix for #32 that sounds great and close this one |
Fixes #32 (verified on Windows 11)