-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
ydotool mousemove --absolute
moves Mouse to the top of the Screen
#250
Comments
any progress on this matter? |
did you see this comment in the help? |
yes pointer acceleration is turned off in the settings |
Disabling pointer acceleration helped. Thanks jonas! I've read that I needed to do that but it slipped my mind still. Edit: Oh, but it seems to be inconsistent at it though. Sometimes it will go to specified location and sometimes it will go to the corner... Edit2: I think I've figured this out? When I try multiple relative mousemove commands at once to achieve the same effect as when using 'absolute' argument I'm experiencing a very similar issue where the commands work randomly. When trying them one by one repeatedly using separate shortcuts for each command they worked flawlessly. So depending on how this 'absolute' argument is handled in the backend a small pause between the actions may do the trick. Edit3: Something like |
I don't have an option to turn off mouse accel in Debian KDE, I only get "Flat" and "Adaptive" in Mouse settings. A workaround which works is to set absolute to 0,0 to move cursor to 0,0 and then use relative to achieve the desired absolute position. Works for my use case. |
I have the same problem. I am using KDE with Fedora 41. I turned off mouse acceleration but it didn't help. I am using the same workaround as mashrit. |
@davidlevner |
Same issue but disabling pointer accelration didn't fixed. |
ydotool mousemove --absolute
just moves the Mouse to the upper left Corner of the Screen, no matter which coordinates are entered.The text was updated successfully, but these errors were encountered: