github-starred/barrier

Fork 0

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

[GH-ISSUE #1108] Edge detection fails with DPI other than 100% #886

New issue

Open

opened 2026-05-05 07:14:44 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:14:44 -06:00

Owner

Originally created by @oilcan-productions on GitHub (Mar 25, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1108

My Server is Windows 10 20H2 (does not really matter was the same issue before)
My Server has 2 monitors
M1 = Laptop Display (Main)
M2 = Display Port Monitor

I set my DPI on both to 150% (Recommended)

My clients are Windows 10 20H2, Raspberry Pi, Mac OS Big Sur (latest)

the config is

            RaspberryPi
                 |
MacOS  -- Server M1 -- Server M2 -- Win10

With DPI set to 150% on the Server I can move from M1 to MacOS or RaspberryPi
From M2 I cannot move to Win10
When I set the DPI to 100% on both displays of the Server I can move between all displays successfully.
When I move Win10 Below M1 I can move to it regardless of the DPI settings
From the log it seems that with DPI != 100% the edge of M2 is not detected at all as I don't see the event in the logs.

Originally created by @oilcan-productions on GitHub (Mar 25, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1108 My Server is Windows 10 20H2 (does not really matter was the same issue before) My Server has 2 monitors M1 = Laptop Display (Main) M2 = Display Port Monitor I set my DPI on both to 150% (Recommended) My clients are Windows 10 20H2, Raspberry Pi, Mac OS Big Sur (latest) the config is ``` RaspberryPi | MacOS -- Server M1 -- Server M2 -- Win10 ``` With DPI set to 150% on the Server I can move from M1 to MacOS or RaspberryPi From M2 I cannot move to Win10 When I set the DPI to 100% on both displays of the Server I can move between all displays successfully. When I move Win10 Below M1 I can move to it regardless of the DPI settings From the log it seems that with DPI != 100% the edge of M2 is not detected at all as I don't see the event in the logs.

gitea-mirror commented

2026-05-05 07:14:48 -06:00

Author

Owner

@verglor commented on GitHub (Mar 30, 2021):

I have similar problem with 3 monitors in row on my Win10 server and one macOS Catalina client below them.
If all my server monitors have the same DPI everything works fine. Once they have different DPI from each other, I cannot move to macOS client via edge however I can move from client to server.

@verglor commented on GitHub (Mar 30, 2021): I have similar problem with 3 monitors in row on my Win10 server and one macOS Catalina client below them. If all my server monitors have the same DPI everything works fine. Once they have different DPI from each other, I cannot move to macOS client via edge however I can move from client to server.

gitea-mirror commented

2026-05-05 07:14:49 -06:00

Author

Owner

@neakmenter commented on GitHub (May 26, 2021):

I have the same issue here. main 4k screen is 250% scaling, 1080 screen 'above' and 1080 screen on the left both at 100%. want to "barrier" over to surface pro 3 screen on the right. It works if I place both my 1080 screens to the left of the main screen, or if I disconnect one of them. But will not work with my usual setup unless I reduce scaling to less than 150% on the main screen. I've been using a keyboard shortcut to get to the surface screen, but it's far less intuitive. (the cursor will 'return' to the server just fine, just can break through to the client!)
Just tried something - it works if I arrange my monitors like this screen...

@neakmenter commented on GitHub (May 26, 2021): I have the same issue here. main 4k screen is 250% scaling, 1080 screen 'above' and 1080 screen on the left both at 100%. want to "barrier" over to surface pro 3 screen on the right. It works if I place both my 1080 screens to the left of the main screen, or if I disconnect one of them. But will not work with my usual setup unless I reduce scaling to less than 150% on the main screen. I've been using a keyboard shortcut to get to the surface screen, but it's far less intuitive. (the cursor will 'return' to the server just fine, just can break through to the client!) Just tried something - it works if I arrange my monitors like this screen... ![image](https://user-images.githubusercontent.com/69205639/119714955-5ad2d500-be5b-11eb-81b7-eb6a82549441.png)

No labels

Rows
Columns