input-leap VS ddcutil

There is an actively developed fork https://github.com/input-leap/input-leap, however that fork is still undergoing heavy development and recommends sticking with Barrier until they're able to release v3.0.0 which they expect rather soon.

barrier is basically a dead project now. The active members of the project forked it and are going to release when ready but

https://github.com/input-leap/input-leap

Keep an eye on that for anything new

There's a new fork of barrier called input leap (not to be confused with the leap motion), https://github.com/input-leap/input-leap with work on getting Wayland support in shape. Not sure how far the support is atm, but the gnome 45 release notes mentioned "Wayland support for Input Leap" (https://release.gnome.org/45/)

Wayland tracker issue, https://github.com/input-leap/input-leap/issues/109

I wonder if I would be better off just buying a LG monitor without the Smart KVM, and instead using Barrier (or, Input Leap, which seems to be maintained actively compared to Barrier https://github.com/input-leap/input-leap)

Could also be worth mentioning that Barrier is basically unmaintained at this point so you'll probably never get Wayland support there. The maintainers (apparently the owner of the debauchee/barrier dropped off the face of the earth) of Barrier forked it and migrated to input-leap (issue with details if interested) which is where all development is presently, although they haven't made a release yet.

I'm already using waynergy with input-leap as my main way to control the laptop when it is docked. It is amazing.

Apologies. I hate when people do that as well.

In addition to the other links posted, ddcutil.org has some more good info: https://www.ddcutil.com/#introduction

Sous Linux j'avais utilisé ddcutil

Most monitors have a Virtual Control Panel (VCP), which implements features defined in the Monitor Control Command Set (MCCS). This is a VESA standard. You can find the Input selection command in table 8-10. You send these commands over an I2C bus called Display Data Channel/Command Interface which is yet another VESA standard. If you are running Windows https://www.nirsoft.net/utils/control_my_monitor.html will let you use every VCP feature your monitor has. For Linux, https://www.ddcutil.com/ does this. For Mac, https://github.com/alin23/Lunar

The protocol is called DDC , it's a VESA standard. In there, it's called VCP features. If you are running Windows https://www.nirsoft.net/utils/control_my_monitor.html will let you use every VCP feature your monitor has. For Linux, https://www.ddcutil.com/ does this. For Mac, https://github.com/alin23/Lunar note how all three mention input selection.

ddcutil (a command-line tool, and what most UI tools are based on)

A related non rust tool (that also has an optional GUI) is ddcutil. How does this compare to that?

I've also used ddcui: https://www.ddcutil.com/#introduction, available as an AUR package: https://github.com/rockowitz/ddcutil. This has a nice GUI: https://www.ddcutil.com/screenshots/ddcui_features.png and works on everything I've tried it on out of the box.