Chordie VS input-leap

Hope you like it. You can find some pics and videos in the gallery. There's a full guide and chord cheat sheet on my Github.

It's very easy, just like any other encoder. One example can be found here.

For a working I2C expander based keyboards you can check my IIIC and Chordie. Sadly you can't get away from writing your own matrix scanning as there's no easy way to make reading I2C expander states in QMK. MCP23017 and MCP23018 have the same register addresses so there's no problem with moving the code between those two.

You might want to check my chording keyborard Chordie. It's 3D printable/handwired. Also making use of ASETNIOP just like Ginny but this one is running on /r/DennyTom engine and has a bit more features than Ginny.

Welcome to the Keyboard&Trackball family. Once you start using such a combo there's no going back. I have just attached one to my updated IIICC. Still work in progress but since I started using Chordie with trackball I knew I can't go back to keyboard + mouse. Reaching out to mouse is so annoying.

Typing with a pen on a virtual keyboard sounds slow, I'd be looking into an ergonomic split keyboard or a chorded keyboard instead.

You can try https://github.com/kbjunky/Chordie

Hi all! I'm the creator of Chordie. Thank you very much for all the comments and upvotes! I am glad that you find my project interesting. /u/_eLRIC already posted all the relevant links so I will only add project page on my Github. You can also find some other interesting projects there like breakout boards for mouse sensors, namely ADNS9800 and PMW3360.

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.