github-starred/barrier

Fork 0

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

[GH-ISSUE #1157] Mouse couldn't move over when client is below server #928

New issue

Open

opened 2026-05-05 07:17:47 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:17:47 -06:00

Owner

Originally created by @latteye on GitHub (May 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1157

Describe the bug
3 Devices
1: server -- pc with 2 monitor
2: MacBook -- on left
3. SurfaceBook with Win 10 , below server.

There is no "INFO: leaving screen" log when I move the mouse to the bottom of server's screen.
I have tried move my SurfaceBook Virtual Device on Left and on Above, both works. Only below the server doesn't work.

But I can move mouse back from client to server on the top of client edge.

OS: 2 Win 10 and 1 OSX
Barrier version: All 2.3.3

Originally created by @latteye on GitHub (May 8, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1157 **Describe the bug** 3 Devices 1: server -- pc with 2 monitor 2: MacBook -- on left 3. SurfaceBook with Win 10 , below server. There is no "INFO: leaving screen" log when I move the mouse to the bottom of server's screen. I have tried move my SurfaceBook Virtual Device on Left and on Above, both works. Only below the server doesn't work. But I can move mouse back from client to server on the top of client edge. - OS: 2 Win 10 and 1 OSX - Barrier version: All 2.3.3

gitea-mirror commented

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

Author

Owner

@lucas2595 commented on GitHub (May 28, 2021):

@latteye , is there any dead area between the server screen and your client below it? Barrier doesn't "jump over" dead areas, so that's one possibility.

@lucas2595 commented on GitHub (May 28, 2021): @latteye , is there any dead area between the server screen and your client below it? Barrier doesn't "jump over" dead areas, so that's one possibility.

gitea-mirror commented

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

Author

Owner

@latteye commented on GitHub (Jun 10, 2021):

hmm? how to define dead area?
My taskbar is on the top of the screen. (but move from top is working)

@latteye commented on GitHub (Jun 10, 2021): hmm? how to define `dead area`? My taskbar is on the top of the screen. (but move from top is working)

gitea-mirror commented

2026-05-05 07:17:50 -06:00

Author

Owner

@latteye commented on GitHub (Jun 10, 2021):

oh , do you mean the dead corner which I can define in barrier?
No I didn't enable any dead corner on server bottom

@latteye commented on GitHub (Jun 10, 2021): oh , do you mean the `dead corner` which I can define in barrier? No I didn't enable any `dead corner` on server bottom

gitea-mirror commented

2026-05-05 07:17:50 -06:00

Author

Owner

@lucas2595 commented on GitHub (Jun 10, 2021):

@latteye , sorry but no. I mean this:

You can't cross from server to client over dead areas, because you can't reach the bottom of the green dead area. This happens when you have different monitors with different positions or resolutions that don't fit a rectangle perfectly.

Does this relate to your setup?

@lucas2595 commented on GitHub (Jun 10, 2021): @latteye , sorry but no. I mean this: ![image](https://user-images.githubusercontent.com/24466413/121571718-becbd080-c9f9-11eb-9d5c-e17111b00c2f.png) You can't cross from server to client over dead areas, because you can't reach the bottom of the green dead area. This happens when you have different monitors with different positions or resolutions that don't fit a rectangle perfectly. Does this relate to your setup?

gitea-mirror commented

2026-05-05 07:17:51 -06:00

Author

Owner

@latteye commented on GitHub (Jun 23, 2021):

Yes. Very similar.
I have a 4K on the left and a 1080x1920 monitor on the right. I can't cross from both monitor..
ah..
Would this be consider as a bug and get fix?

@latteye commented on GitHub (Jun 23, 2021): Yes. Very similar. I have a 4K on the left and a 1080x1920 monitor on the right. I can't cross from both monitor.. ah.. Would this be consider as a bug and get fix?

No labels

Rows
Columns