-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Pointer broken on multi-monitor systems where one or more monitors use scaling #64
Comments
I am unable to reproduce this with headless displays. Which versions do you have of wayvnc and wlroots? |
wlroots-git - 0.11.0.r44.gbae8d759-1 And specifically, I have one 3840x2160 display, scale 2.0, and 1920x1080 display, scale 1.0. And I was using the iOS VNC app, VNC Viewer - Remote Desktop. |
Yes, this may have to do with running with RealVNC's "official" iOS app. I now have another bug to report with VNC Viewer and wayvnc. |
Do I need to enable full mouse coordinate logging to track this down? |
This is still an issue with VNC Viewer. I don't know any other VNC client to try. |
I figured it out. The absolute pointer api isn't constrained to a given output. The absolute cursor space encompasses the entire seat, with no handle to specify a single output. |
Ah, different than I thought. wlroots supports that, but Wayfire is ignoring it in their implementation. I will report it there. |
So this isn't technically your issue, I can close this one. |
This is a redux of a previous issue, only this time, one or more of the outputs use scaling. In this case, I have a 3840x2160 primary monitor that is using 2.0 scaling so it has an effective resolution of 1920x1080, but visible resolution that is double that. The secondary monitor is 1920x1080 with a 1.0 scale.
The result of this scale and arrangement of outputs, is that the cursor seems to move vertically properly, but horizontally, it appears to span both monitors while it is moving across the one output in the VNC client. When the VNC client is on the secondary output, the cursor appears to only work on the visible output when it is on the right half of the VNC client, otherwise it clicks on the primary output.
The text was updated successfully, but these errors were encountered: