mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #757] Feature request: send command to HDMI switch #594
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#594
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 @VE3NEA on GitHub (Jun 19, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/757
When switching the mouse and keyboard between the screens, send a source selection command to the HDMI switch so that the monitor is switched as well. This will turn barrier from KM into a true KVM.
I am using barrier to switch the keyboard and mouse, and this HDMI switch to switch the monitor. All works fine, except that to switch the screens, I have to press both the barrier hotkey and the button on the switch.
It would be nice if the user could specify the RS232 port settings and the source switch command in the UI, and barrier would send this command to the specified COM port when switching the screens.
As a P.O.C., I have written code that sends the command to the switch on Windows, using my own
hard-coded port settings and commands. A complete solution will require some extra code to edit and store the settings.
@VE3NEA commented on GitHub (Jun 19, 2020):
Here is the pull request for my P.O.C. code. It works fine on my system and could be used as part of the complete solution.
@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.
@shymega commented on GitHub (Sep 25, 2020):
This is still being worked on. Adding bot mitigation label.