mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1182] Feature request: Share only mouse/keyboard option #953
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#953
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @j3sh on GitHub (Jun 2, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1182
Feature description
Is there any option to implement an option to block sharing mouse or keyboard on the server? For example, I'm using a Logitech mouse, which has an option to switch between device. But the keyboard is connected with my PC by cable, and it would be more comfortable to use only one with my Mac to work. User can switch between clients with defined keyboard shortcut.
Mouse is working more accurately/precisely when use native connection than sharing.
@antiquitte commented on GitHub (Aug 19, 2021):
I have the same use case as described above.
Using Logitech Flow to handle mouse switching works great, but I have a problem when it comes to holding down a key and pressing the mouse (ex. hold down shift and click mouse to select text). When the mouse is pressed, Barrier input is disabled on the client and resumes after the click is done.
Maybe this could be solved by only allowing sharing of the keyboard and setting a hotkey to change between server and client.
@antiquitte commented on GitHub (Aug 19, 2021):
The issue seems to be fixed after enablingFix Preserve Focusfor the client.That was a lie...