forked from deskflow/deskflow
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Windows 10 scaling not supported under certain circumstances #1462
Comments
Same issue -- 2.4.0 is broken for me under Windows 11. Main monitor (server) at 150%. Mouse jumps to adjacent barrier screen at wrong location and can never come back. 2.3.4 fixes things. |
Im experiencing same issue with 150% scalling on windows using 2.4.0 |
mipedja
added a commit
to mipedja/barrier
that referenced
this issue
Jan 7, 2022
Fixes regression from debauchee#304 Fixes debauchee#1462, debauchee#1443, possibly others.
mipedja
added a commit
to mipedja/barrier
that referenced
this issue
Jan 8, 2022
Fixes regression from debauchee#304 Fixes debauchee#1462, possibly others.
1 task
Same issue here, please fix :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When my Win 10 PC (server, on the left side) is configured to scale to 125%, I cannot use it as a server together with my Mac (client on the right side), because when it moves from one to the other, when arriving to 3/4 of the PC screen, it immediately jumps to the bottom right corner of the Mac and makes the whole sharing useless until I disable the client on the Mac. As soon as I switch to 100% scaling, everything's ok again. So what I did is downgraded the PC to 2.3.4, and it seems to be working fine again, as it was for more than a year with 2.3.3.
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
No response
What OSes are you seeing the problem on? (Check all that apply)
Windows, macOS
What OS versions are you using?
Server 10.0.19042.1348
Client Monterey 12.0.1
Relevant log output
No response
Any other information
No response
The text was updated successfully, but these errors were encountered: