I absolutely love the glkvm native client. I've been using it on both MacOSX and Android. I know it's not OSS and this is obviously not its repo.
I have a few feature requests that, if implemented, would improve its usability. In particular, I think the last one would be a life-changer for many and remove a huge source of frustration.
-
when no video signal is detected, still allow to send some characters to attempt to wake the screen up (this removes the need for caffeine/amphetamine and also saves the screen of the target device and lengthens its expected life span)
-
introduce a UI element to perform a reboot even before having been able to connect to the remote desktop
-
introduce a software listener for wake on lan, such that if the KVM is already up, you could power-cycle it the same way you would normally power it on (this removes the need for a smart socket)
-
I would really really appreciate if you could add a modality where you leverage accessibility features on the client device to capture all keyboard input and pass along key combinations such as CMD-TAB or CMD-`, from both MacOSX and Android external and bluetooth keyboards. The caps lock could be hijacked to toggle this behavior on and off, and its LED indicator could show the user whether it is currently on or off.
Thank you!
I absolutely love the glkvm native client. I've been using it on both MacOSX and Android. I know it's not OSS and this is obviously not its repo.
I have a few feature requests that, if implemented, would improve its usability. In particular, I think the last one would be a life-changer for many and remove a huge source of frustration.
when no video signal is detected, still allow to send some characters to attempt to wake the screen up (this removes the need for caffeine/amphetamine and also saves the screen of the target device and lengthens its expected life span)
introduce a UI element to perform a reboot even before having been able to connect to the remote desktop
introduce a software listener for wake on lan, such that if the KVM is already up, you could power-cycle it the same way you would normally power it on (this removes the need for a smart socket)
I would really really appreciate if you could add a modality where you leverage accessibility features on the client device to capture all keyboard input and pass along key combinations such as CMD-TAB or CMD-`, from both MacOSX and Android external and bluetooth keyboards. The caps lock could be hijacked to toggle this behavior on and off, and its LED indicator could show the user whether it is currently on or off.
Thank you!