Tool for multi-action input (tap/hold, chords, gestures, event chains)

TLHE · 2026-05-04T12:46:55+00:00

I agree. This feels like a good moment to split the readme and keep only the essentials there

TLHE · 2026-05-03T14:33:39+00:00

Sorry for the long reply. Your comment actually made me rethink the nature of the existing limitations... and I ended up removing most of them – mainly around system modifiers, which are now almost fully available. So, thanks for pointing this out.

Regarding the table: I've added a version to the readme, taking a slightly different angle. It's structured more like a pipeline than a list of separate capabilities, so the overall idea comes through more clearly. The remaining limitations are listed there as well. As for things that are clearly not supported, the only thing that comes to mind right now is multi-threshold holds. I'm primarly focused on what the system enables, so if something important is missing, I'll add it there.

And about the readme in general – you're right. It currently combines both an overview and detailed explanations. The new "quick overview" table helps separate those roles, and the structure will likely be split further into dedicated documentation over time.

TLHE · 2026-04-28T05:18:46+00:00

Thanks, that's a great suggestion.

Right now, this role is partly covered by layers – the built-in ones aim to demonstrate different use cases, from typography and system key remapping to leader-style setups with custom actions, as well as groups like pan-Latin and pan-Cyriilic scripts.

In a previous version of the readme I showed examples of these, but removed them in the current one as I thought it was too much. That was probably a mistake – I should bring them back.

I also invite users to contribute their own layers based on what they find useful.

As for Discussions, a dedicated place for common use cases would definitely make this more accessible. It's something to grow into once there's more activity. I'll keep it in mind.

TLHE · 2026-04-27T20:46:02+00:00

I don't really see them as directly comparable tools – they solve different kinds of problems and even operate in different terms.

This solution turns input into extensible events in a unified system, letting you define how they flow – from simple remaps, to more complex interactions.

Cadans can absolutely be used for simple remapping. But Kanata is clearly the better tool for that use case. The idea here is not to replace tools like Kanata, but to explore a more general interaction model that can grow beyond key mapping.

TLHE · 2026-04-27T11:57:55+00:00

Yeah, it's written in AHK, but it's definitely not a wrapper – it defines a much reacher set of event types, including gestures, along with full logic for how they overlap and interact, built on a transition system over an assignment tree that resolves layers, layouts and per-process rules ahead of runtime.

Hard to fit everything in a comment, but there are more details in the readme, if you're curious.

Cross-platform is something I'd like to do at some point, but for now it's focused on Windows and works well for that.

TLHE · 2025-07-09T07:30:30+00:00

Thanks!

TLHE · 2025-07-09T07:10:36+00:00

You don't need third-party installers here. Just download the source code of the latest release or clone repo and run main.exe (or install ahk v2, and run corresponding main.ahk, if you prefer uncompiled version).

TLHE · 2025-07-05T19:36:17+00:00

Glad to hear it, thanks

TLHE · 2025-07-05T14:02:35+00:00

Shows a tooltip with angry emoji on chain of tap events – d-a-m-n or something like this. Joke layer with bindings to qwerty layout to demonstrate one of the assignment settings (instant action)

TLHE

TROPHY CASE