| > The project's description is shit. I dunno man, this worked pretty ok for me: > This utility watches for USB device connect/disconnect events and switches monitor inputs via DDC/CI. And then a couple lines latter, a sample config that makes it pretty obvious how simple this goes: > usb_device = "1050:0407" \ on_usb_connect = "Hdmi1" \ on_usb_disconnect = "Hdmi2" Plug in a device & switches to hdmi1. Unplug & it switches to hdmi2. A USB switch is optional, one could just move where they plug their mouse into by hand, for example. But you don't seem to be interested in helping fill yourself in on anything here, on learning, on using search engines to find anything out. Honestly filling in the neophyte knowledge like that is not what project descriptions are for, in my book. Generally, dude: relax, chill out. Most everything on this planet could use better description. But this seemed pretty clear & simple to me, at least. I think it'll work for a lot a lot of people as is. No need to be aggressively rude. Have you ever dealt with any kind of soft-kvm like technology before? Perhaps people would more self-select into this kind of project, versus rando's walking in on the street. I think that's ok. |
A "USB switch" reads like a switch with a USB cable on it, that the computer it is plugged into can see when it changes. Which is fine, except the fact that a keyboard and mouse are also presumed to be plugged in is not said or hinted.
"DDC/CI" is similarly undefined. A program switching video inputs makes no sense: a computer produces video output, not input. You would need to know the program is sending commands to the monitor to tell that to switch to a different input.
Both of these facts could easily have been in the first sentence. Without, the whole article is noise.