Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: send command to HDMI switch #757

Closed
ghost opened this issue Nov 4, 2021 · 0 comments
Closed

Feature request: send command to HDMI switch #757

ghost opened this issue Nov 4, 2021 · 0 comments
Labels
feature-request Internal label used for moving Feature Requests work-in-progress Currently being worked on

Comments

@ghost
Copy link

ghost commented Nov 4, 2021

This issue has been migrated from old Barrier Github repository debauchee/barrier#757

Issue created on: 2020-06-19 by @VE3NEA
Issue last updated on: 2020-09-25

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.


Commented on: 2020-06-19 by @VE3NEA

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.


Commented on: 2020-09-19 by @github-actions[bot]

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.


Commented on: 2020-09-25 by @shymega

This is still being worked on. Adding bot mitigation label.

@ghost ghost added the work-in-progress Currently being worked on label Nov 10, 2021
@shymega shymega added the feature-request Internal label used for moving Feature Requests label Nov 19, 2023
@input-leap input-leap locked and limited conversation to collaborators Nov 19, 2023
@shymega shymega converted this issue into discussion #1767 Nov 19, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
feature-request Internal label used for moving Feature Requests work-in-progress Currently being worked on
Projects
None yet
Development

No branches or pull requests

1 participant