[GH-ISSUE #751] Feature Request: Mutual share option #586

New issue

Closed

opened 2026-05-05 06:43:36 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

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

Owner

Originally created by @adyanth on GitHub (Jun 15, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/751

Having a mutual share option would be of great assistance when there are multiple PCs and multiple peripherals (mouse needed for one, keyboard only for another), and we don't need to check which controls what before using it.

Originally created by @adyanth on GitHub (Jun 15, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/751 Having a mutual share option would be of great assistance when there are multiple PCs and multiple peripherals (mouse needed for one, keyboard only for another), and we don't need to check which controls what before using it.

gitea-mirror closed this issue

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

gitea-mirror commented

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

Author

Owner

@theycallmeloki commented on GitHub (Jun 16, 2020):

+1 for having this feature can confirm things act flaky if you try to add multiple servers and clients to try and multiplex this feature on your own

@theycallmeloki commented on GitHub (Jun 16, 2020): +1 for having this feature can confirm things act flaky if you try to add multiple servers and clients to try and multiplex this feature on your own

gitea-mirror commented

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

Author

Owner

@adyanth commented on GitHub (Jun 16, 2020):

To start with, it can be as simple as, having the server running all the time, and we can provide the client on both PCs, so that two of them can use each other's peripherals.

@adyanth commented on GitHub (Jun 16, 2020): To start with, it can be as simple as, having the server running all the time, and we can provide the client on both PCs, so that two of them can use each other's peripherals.

gitea-mirror commented

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

Author

Owner

@theycallmeloki commented on GitHub (Jul 9, 2020):

If someone can point me to how this would be implemented I can try and submit a PR

@theycallmeloki commented on GitHub (Jul 9, 2020): If someone can point me to how this would be implemented I can try and submit a PR

gitea-mirror commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Sep 19, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 19, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

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

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

I think that this is not easily possible in the current codebase. Basically we would need to change the basic design of how Barrier works. Unfortunately adding workarounds like multiple clients is not viable, as Barrier server currently assumes that there are no clients on the machine it's running on and implementing this would complicate whole codebase for little gain.

@p12tic commented on GitHub (Jan 10, 2021): I think that this is not easily possible in the current codebase. Basically we would need to change the basic design of how Barrier works. Unfortunately adding workarounds like multiple clients is not viable, as Barrier server currently assumes that there are no clients on the machine it's running on and implementing this would complicate whole codebase for little gain.

gitea-mirror referenced this issue

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

[PR #846] [MERGED] Add BARRIER_BUILD_TESTS and BARRIER_USE_EXTERNAL_GTEST CMake options #1707