qmk_firmware VS evsieve

I had trouble with HMR as well at the beginning, but since switching to sunaku's fork/PR I've almost eliminated all the issues I had with it. And worth mentioning is urob's timeless HMR config from which I think the fork/PR takes some of its inspiration.

Affirmative. I updated my fork and my clone last week. I also did a second, fresh clone and merged this PR: https://github.com/manna-harbour/qmk_firmware/pull/56

Im guessing installing something like this is what i need to do? https://github.com/manna-harbour/qmk_firmware/pull/56

See my Miryoki PR for details: https://github.com/manna-harbour/qmk_firmware/pull/56

I have a separate system for that as part of this old unreleased project. They're orthogonal so could be used together, but it'd be nicer if they were integrated. If you just want to remap buttons or map buttons to keys you can do that in the OS.

Well, things like Bilateral Combinations are aware of which hand is using the modifier to only apply it to the other side's presses & minimise accidental triggering on same-hand rolls.

Same with evsieve: I can see the keys I press, like in wev, but the remap doesn't work for the keyboard or the mouse:

My best suggestion for you is to leverage evsieve: https://github.com/KarsMulder/evsieve

There are many other software tools such as https://github.com/jtroo/kanata and https://github.com/KarsMulder/evsieve. The main difference with 𝑥MK is that you can use native QMK and ZMK.

Ironically I know you can do this in i3 and xorg/gnome using xmodmap or editing the xkb file. I'm pretty sure wayland compositors should be able to read xkb-compliant files but the recommended way of loading that in is probabaly different between various compositors? You could also use a "second generation" interception tool that works at the event device level.

You might want to try evsieve, it even has an example about toggling devices and it concludes with a hint on how to get this to work for 2 VMs.

Evsieve is amazing in general you sould check it out 🙂

evsieve has solved that for me, as the virtual device created is always available; it starts when I log on my computer and stay open forever.

evsieve can remap. I haven't used it yet but you can find it here: https://github.com/KarsMulder/evsieve

If this feels a bit limited (you have a few predefined options), there's also evsieve. Which allows you to do a lot more (like selective key pass-through, shortcuts, etc.).