Setting to control the X and Y of mouse position when jiggling #1073

New issue

Open

opened 2026-02-20 14:10:41 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 14:10:41 -05:00

Owner

Originally created by @CDx4f3kCAf3Y on GitHub (Sep 1, 2025).

Is your feature request related to a problem? Please describe.
I updated my PiKVM yesterday after using it for over a year in production with no problems! (Thank you for such an awesome product.)
I noticed today that I've mouse jiggling is not working as expected.
I tracked it down to commit github.com/pikvm/kvmd@72c9ae3aa0.
I have become accustomed to the mouse jigging occurring in the very center of my screen.
Some of my work occurs on remote server desktops. When I do this work, the remote desktop application is setup in window mode, so I can still see other parts of my screen which are not on the remote server. I've learned to keep the remote desktop window positioned so that the center point of my screen overlaps the remote desktop window. With this setup, the former mouse giggling would keep the screensaver from activating on both systems. Now, if the mouse is not positioned over the remote desktop window, the remote server does not receive the jiggles and goes to screensaver.

Describe the solution you'd like
I would like a setting that (when enabled) causes the mouse jiggling to occur at the center of the screen (pre-commit behavior) instead of the at the last mouse position (post-commit behavior).

Describe alternatives you've considered
Two alternatives would be:

Have a setting that specifies the coordinates where the mouse jiggling should occur (use this to specify some other static location besides the center of the screen)
Patching the Python files to restore the old functionality, but I do not want to have to maintain custom "patches" or workarounds.

Additional context
Add any other context or screenshots about the feature request here.

Originally created by @CDx4f3kCAf3Y on GitHub (Sep 1, 2025). **Is your feature request related to a problem? Please describe.** I updated my PiKVM yesterday after using it for over a year in production with no problems! (Thank you for such an awesome product.) I noticed today that I've mouse jiggling is not working as expected. I tracked it down to commit https://github.com/pikvm/kvmd/commit/72c9ae3aa00b8817fab2b8243203ca6e1c25e146. I have become accustomed to the mouse jigging occurring in the very center of my screen. Some of my work occurs on remote server desktops. When I do this work, the remote desktop application is setup in window mode, so I can still see other parts of my screen which are not on the remote server. I've learned to keep the remote desktop window positioned so that the center point of my screen overlaps the remote desktop window. With this setup, the former mouse giggling would keep the screensaver from activating on both systems. Now, if the mouse is not positioned over the remote desktop window, the remote server does not receive the jiggles and goes to screensaver. **Describe the solution you'd like** I would like a setting that (when enabled) causes the mouse jiggling to occur at the center of the screen (pre-commit behavior) instead of the at the last mouse position (post-commit behavior). **Describe alternatives you've considered** Two alternatives would be: - Have a setting that specifies the coordinates where the mouse jiggling should occur (use this to specify some other static location besides the center of the screen) - Patching the Python files to restore the old functionality, but I do not want to have to maintain custom "patches" or workarounds. **Additional context** Add any other context or screenshots about the feature request here.

deekerman commented

2026-02-20 14:10:43 -05:00

Author

Owner

@cRoCx commented on GitHub (Oct 12, 2025):

I'm no official here, but I wouldn't give many hopes into your request. The pre-commit behaviour was most likely a quick-and-dirty solution for the post-commit behaviour, as that is the one how it probably should have been in the first place. These jigglers are usually not supposed to manipulate mouse position to completely new coordinates. They jiggle around the current mouse position and go back to this mouse position after the jiggling is done.

It might not solve your problem if you need to handle remote servers, but I just want to mention there is also other software for this in general like Autohotkey scripts out there for this ... or a programmable Arduino USB key.

@cRoCx commented on GitHub (Oct 12, 2025): I'm no official here, but I wouldn't give many hopes into your request. The pre-commit behaviour was most likely a quick-and-dirty solution for the post-commit behaviour, as that is the one how it probably should have been in the first place. These jigglers are usually not supposed to manipulate mouse position to completely new coordinates. They jiggle around the current mouse position and go back to this mouse position after the jiggling is done. It might not solve your problem if you need to handle remote servers, but I just want to mention there is also other software for this in general like Autohotkey scripts out there for this ... or a programmable Arduino USB key.