mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 14:15:52 -06:00
[GH-ISSUE #343] Odd mismatching vertical / horizontal sensitivity #178
Labels
No labels
Xorg
documentation
enhancement
macos
pull-request
question
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/lan-mouse#178
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FabulousCupcake on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/343
As I was trying multiple software kvm switch applications I noticed the input emulation on windows seems to be more sensitive vertically than horizontally with lanmouse.
Unfortunately I don't have an objective way to measure this.
The best test I could devise is to repeatedly flick my cursor 45° diagonal between two points in my input-capture screen, and do the same in the input-emulated screen. With lanmouse, I always overshoot vertically (upwards to top-right, downwards to bottom-right).
I realize this issue is probably not too helpful, but I hope it may be useful to track if more people encounter similar problem.
Setup
Input Capture: Mac, native resolution 3840x2160, logical resolution 3008x1692
Input Emulation: Windows, 2560x1440
Version:
35773dfd07@feschber commented on GitHub (Oct 31, 2025):
I'm pretty sure, this is not the input-emulation on the windows side but rather the capture on MacOS. I'm aware of this problem and currently trying to fix some issues on the MacOS side.
@feschber commented on GitHub (Oct 31, 2025):
Might be related:
https://github.com/feschber/lan-mouse/pull/131#discussion_r1602176713
@feschber commented on GitHub (Oct 31, 2025):
Closing for now. Feel free to reopen, if this doesn't resolve things for you!
@FabulousCupcake commented on GitHub (Oct 31, 2025):
Yes! It is resolved, thank you!