github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1462] Windows 10 scaling not supported under certain circumstances #1119

New issue

Closed

opened 2026-05-05 07:30:20 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 07:30:20 -06:00

Owner

Originally created by @sgrienen on GitHub (Dec 2, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1462

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

Originally created by @sgrienen on GitHub (Dec 2, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1462 ### 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_

gitea-mirror closed this issue

2026-05-05 07:30:21 -06:00

gitea-mirror commented

2026-05-05 07:30:23 -06:00

Author

Owner

@vvuk commented on GitHub (Dec 3, 2021):

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.

@vvuk commented on GitHub (Dec 3, 2021): 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.

gitea-mirror commented

2026-05-05 07:30:25 -06:00

Author

Owner

@okihus commented on GitHub (Dec 14, 2021):

Im experiencing same issue with 150% scalling on windows using 2.4.0

@okihus commented on GitHub (Dec 14, 2021): Im experiencing same issue with 150% scalling on windows using 2.4.0

gitea-mirror commented

2026-05-05 07:30:26 -06:00

Author

Owner

@mrwensveen commented on GitHub (Dec 14, 2021):

This looks like a regression (#304). The file that fixed this issue is deleted in the current version.
Probably the same issues: #1443, #1423, #1363, possibly others.

@mrwensveen commented on GitHub (Dec 14, 2021): This looks like a regression (#304). The file that fixed this issue is deleted in the current version. Probably the same issues: #1443, #1423, #1363, possibly others.

gitea-mirror commented

2026-05-05 07:30:28 -06:00

Author

Owner

@danielponte commented on GitHub (Oct 20, 2023):

Same issue here, please fix :)

@danielponte commented on GitHub (Oct 20, 2023): Same issue here, please fix :)