[PR #240] [CLOSED] X: Only consider mouse movement on the X screen we were started on #1584

New issue

Closed

opened 2026-05-05 07:56:58 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:56:58 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/debauchee/barrier/pull/240
Author: @jwestfall69
Created: 1/25/2019
Status: ❌ Closed

Base: master ← Head: x-screens

📝 Commits (1)

79fec49 X: Only consider mouse movement on the X screen we were started on

📊 Changes

1 file changed (+5 additions, -0 deletions)

View changed files

📝 src/lib/platform/XWindowsScreen.cpp (+5 -0)

📄 Description

X windows supports running multple X screens per instance of X (ie
:0.0, :0.1, etc) Each of these X screens has its own mouse coordinate
space from 0,0 to resX,resY. This causes issues because barrier isn't
taking into account what X screen its on when determining if it needs to
move to a remote client. Thus just moving your mouse between your X
screens can trigger a jump to a remote client.

This patch makes it so barrier will only consider mouse movements on the
X screen it was started on.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/debauchee/barrier/pull/240 **Author:** [@jwestfall69](https://github.com/jwestfall69) **Created:** 1/25/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `x-screens` --- ### 📝 Commits (1) - [`79fec49`](https://github.com/debauchee/barrier/commit/79fec4909d3b114691b7811f0584d1ee26a77d69) X: Only consider mouse movement on the X screen we were started on ### 📊 Changes **1 file changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/platform/XWindowsScreen.cpp` (+5 -0) </details> ### 📄 Description X windows supports running multple X screens per instance of X (ie :0.0, :0.1, etc) Each of these X screens has its own mouse coordinate space from 0,0 to resX,resY. This causes issues because barrier isn't taking into account what X screen its on when determining if it needs to move to a remote client. Thus just moving your mouse between your X screens can trigger a jump to a remote client. This patch makes it so barrier will only consider mouse movements on the X screen it was started on. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>