[GH-ISSUE #274] Mouse can skip to the client from an application which locks the mouse in if moved fast enough. #220

New issue

Open

opened 2026-05-05 05:42:56 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 05:42:56 -06:00

Owner

Originally created by @Whytefang on GitHub (Mar 27, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/274

Operating Systems

Server: Windows 1809 build 17763.253

Client: Ubuntu 18.04.2 LTS

Barrier Version

Server is running 2.1.0 RELEASE 0b2dfd80.
Client is running 2.1.0 snapshot 00000000.

Steps to reproduce bug

In a game such as League of Legends, which I play in windowed mode with the cursor locked in the window, moving the mouse quickly enough towards the client screen causes Barrier to move the mouse to the client despite the fact it should not leave the window on regardless of speed. There are about 100 pixels between the edge of the game client and the edge of the screen so it's not that it's a full screen game or anything.

Other info

When did the problem start to occur? I've been noticing it for a few weeks at least, but I haven't done any updates to Barrier that cause it to the best of my knowledge; I likely just wasn't aware it was happening to begin with.
Is there a way to work around it? Yes, you can just not move the mouse too quickly, but it is frustrating.
Does this bug prevent you from using Barrier entirely? No.

Originally created by @Whytefang on GitHub (Mar 27, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/274 ### Operating Systems ### Server: Windows 1809 build 17763.253 Client: Ubuntu 18.04.2 LTS ### Barrier Version ### Server is running 2.1.0 RELEASE 0b2dfd80. Client is running 2.1.0 snapshot 00000000. ### Steps to reproduce bug ### In a game such as League of Legends, which I play in windowed mode with the cursor locked in the window, moving the mouse quickly enough towards the client screen causes Barrier to move the mouse to the client despite the fact it should not leave the window on regardless of speed. There are about 100 pixels between the edge of the game client and the edge of the screen so it's not that it's a full screen game or anything. ### Other info ### * When did the problem start to occur? I've been noticing it for a few weeks at least, but I haven't done any updates to Barrier that cause it to the best of my knowledge; I likely just wasn't aware it was happening to begin with. * Is there a way to work around it? Yes, you can just not move the mouse too quickly, but it is frustrating. * Does this bug prevent you from using Barrier entirely? No.

gitea-mirror commented

2026-05-05 05:43:00 -06:00

Author

Owner

@noisyshape commented on GitHub (Apr 9, 2019):

When you're playing games with the mouse, you should disable screen switching with the mouse by pressing scroll lock. If your keyboard doesn't have scroll lock then Windows has an on screen keyboard. You can then use hotkeys to jump to different screens.

@noisyshape commented on GitHub (Apr 9, 2019): When you're playing games with the mouse, you should disable screen switching with the mouse by pressing scroll lock. If your keyboard doesn't have scroll lock then Windows has an on screen keyboard. You can then use hotkeys to jump to different screens.

No labels

Rows
Columns