Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow for mouse translation based on local screen size #1373

Open
jordan30001 opened this issue Jul 22, 2024 · 2 comments
Open

Allow for mouse translation based on local screen size #1373

jordan30001 opened this issue Jul 22, 2024 · 2 comments

Comments

@jordan30001
Copy link

Is your feature request related to a problem? Please describe.
When connecting to a device that has a mirrored output which is larger than than what the PiKVM supports (e.g. the monitor connected to the KVM is outputting 4k, but the GPU on the device is downscaling the output to the KVM to 1080p) the bounding box for the mouse only works within the scaled area (1080p) which causes weird mouse movement when outside of the bounding box and jagged mouse movements when in Absolute Mouse Mode.
(See below image, the red area is the bounding box for the downscaled 4k output, and the black area is the rest of the screen, which is also 4k)
image

Describe the solution you'd like
Add an option to the KVMs web interface to allow for changing of the mouses resolution at runtime. (see below screenshot of where this could be added)
image

Describe alternatives you've considered
Allow for an override within the override.yml settings file to set the absolute mouse mode to use a custom resolution (e.g. 3840x2160), rather than the input size of the video input.
This solution works for me, however, for others it may not be dynamic enough comparatively to an option directly in the KVMs web interface.
@arch1mede
Copy link
Contributor

I'd wait for the dev to make a comment but please be sure you understand that PiKVM cannot influence the target system, this is the same as if you put a 1080p monitor on the system and asked the monitor manufacturer the same question. This is nothing more than an IP reachable monitor/kb/mouse.

@jordan30001
Copy link
Author

jordan30001 commented Jul 28, 2024 •
edited
Loading

Based on the current description of how the KVM works, this should work.

"In absolute mode, the input device transmits the exact coordinates (X,Y) where the cursor should be moved. This is how touchscreens or drawing tablets work."
If this is the case then no modification to the target system is required, other than setting the remote systems resolution to the desired resolution (in this case 4k) to the monitor and scaling the resolution to 1080p to the kvm (which i am not expecting the KVM to do)

If we say the Viewport is 1920x1080 and the target system is 3840x2160:
We can calculate the scales with the following pseudocode

customResolution = (Width: 3840, Height: 2160) // settings file on kvm, or settings in the web interface
Viewport = (Width: 1920, Height: 1080) //the web interfaces viewport resolution
Mouse = (X: 100, y: 150) // current mouse position in the web interfaces viewport
xScale = customResolution.Width / ViewPort.Width // 2
yScale = customResolution.Height / ViewPort.Height // 2
translatedX = Mouse .X * xScale // 200
translatedY = Mouse.Y * yScale // 300

sendAbsolutePosition(translatedX, translatedY)

If in the above pseudocode the viewport is also at a resolution of 3840x2160 then the scale would be a 1:1 ratio and would remove the jagged movement of the mouse on the target system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arch1mede @jordan30001