github-starred/barrier

Fork 0

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

[GH-ISSUE #138] Feature Request: Allow for the mouse to "wrap" around the screens #110

New issue

Open

opened 2026-05-05 05:17:41 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:17:41 -06:00

Owner

Originally created by @TheCire on GitHub (Sep 29, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/138

Feature Request

Operating Systems

All

Client: Any Client

Barrier Version

Any version in the future

Other info

It'd be nice to have a feature to allow for the mouse to "wrap around" the screens so if i move my mouse to the opposite side of the screen to where i entered the client I could have the mouse return to the server and be on the wrapped side. Even though ShareMouse wasn't very good, I did like that feature.

Originally created by @TheCire on GitHub (Sep 29, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/138 ### Feature Request ### ### Operating Systems ### All Client: Any Client ### Barrier Version ### Any version in the future ### Other info ### It'd be nice to have a feature to allow for the mouse to "wrap around" the screens so if i move my mouse to the opposite side of the screen to where i entered the client I could have the mouse return to the server and be on the wrapped side. Even though ShareMouse wasn't very good, I did like that feature.

gitea-mirror added the

enhancement

label 2026-05-05 05:17:41 -06:00

gitea-mirror commented

2026-05-05 05:17:44 -06:00

Author

Owner

@nsk7even commented on GitHub (Oct 8, 2018):

This is possible already, I work with this feature every day.
Just configure the client on both sides of the server and the server on both sides of the client.

Have a look at my config:

section: screens
	servername:
	clientname:
end
section: links
	servername:
		left = clientname
		right = clientname
	clientname:
		right = servername
		left = servername
end

section: options
	keystroke(control+<) = switchInDirection(right)
end

@nsk7even commented on GitHub (Oct 8, 2018): This is possible already, I work with this feature every day. Just configure the client on both sides of the server and the server on both sides of the client. Have a look at my config: ``` section: screens servername: clientname: end section: links servername: left = clientname right = clientname clientname: right = servername left = servername end section: options keystroke(control+<) = switchInDirection(right) end ```

gitea-mirror commented

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

Author

Owner

@TheCire commented on GitHub (Oct 10, 2018):

I just tried that and I keep getting launch errors "duplicate client"

@TheCire commented on GitHub (Oct 10, 2018): I just tried that and I keep getting launch errors "duplicate client"

gitea-mirror commented

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

Author

Owner

@nsk7even commented on GitHub (Oct 10, 2018):

Where do you get this error?
Just to assure you got this right: the config above is the server sided config only. It is launched like this: barriers --config path/to/config.conf
The client is launched like this "C:/Program Files/Barrier/barrierc.exe" -f --debug INFO --name myclientname --ipc --enable-drag-drop --profile-dir "C:\Users\myusername\AppData\Local\Barrier" [serverip]:24800

@nsk7even commented on GitHub (Oct 10, 2018): Where do you get this error? Just to assure you got this right: the config above is the server sided config only. It is launched like this: `barriers --config path/to/config.conf` The client is launched like this `"C:/Program Files/Barrier/barrierc.exe" -f --debug INFO --name myclientname --ipc --enable-drag-drop --profile-dir "C:\Users\myusername\AppData\Local\Barrier" [serverip]:24800`

gitea-mirror commented

2026-05-05 05:17:52 -06:00

Author

Owner

@a7hybnj2 commented on GitHub (Nov 30, 2018):

I can confirm this 'work around' is working. I saved my existing config edited it and then started pointing to the new config. Seems fine.

@a7hybnj2 commented on GitHub (Nov 30, 2018): I can confirm this 'work around' is working. I saved my existing config edited it and then started pointing to the new config. Seems fine.

No labels

Rows
Columns