Modifier timings

[ktunprasert]

I'm wondering if it's possible to adjust the modifier timing? I mainly use this for my work laptop on the go and the problem I run into is for example: Space{A} >> Ctrl{A}
Sometimes this would get triggered when I am typing normally leading me to select all by mistake and overwrite what I'm writing with something else.

[houmain]

Hi, have you tried:
Space{250ms A} >> Control{A}

[ktunprasert]

@ristomatti that's a great way to use it, though it conflicts with how I view the "Modifier" in general. In QMK, I use the settings called "Permissive Hold" which does have a time out link, though if there is a valid combo within the timeout it immediately executes rather than wait for the timeout to finish. This means I can type fast without needing to wait. If the valid combo is not there, it is a passthrough instead (which is the current behaviour).

The modifier to me is virtual layers triggered by holding down (Layer Toggle on Hold), and for you is triggered by key sequencing (Tap Dancing). I think for your case A !100ms B should be the right syntax, but instead of waiting for the timeout it should be able to see if the next immediate sequence exists as a mapping and executes it immediately. This type of behaviour was introduced into Kanata and KMonad as well but they never work as well as QMK native solution does (at least 2 timeout are required, very fiddly). I only wanted to bring this up to see the repo author's opinions on it, I already use this software and I would be very happy to see it as full replacement for QMK.

[ristomatti]

@ktunprasert Agree. My primary use case for Keymapper is application specific shortcuts. I doubt if it's possible to reach the level of precision you'll get out of a hardware solution though.

P.S. I also use QMK w/ 5 layers in addition to i3wm hacks. There's always something to "improve"... Getting it all done through Keymapper would make things quite a lot simpler to manage.

[houmain]

@ktunprasert

The combo should only work when the modifier is held down, is this something that's already implemented but I haven't read about?

No, this is not yet available but I will try to implement it. I am thinking about enhancing Not. So Space{A !A} should trigger when A is released and Space is still hold.
I also intend to change the behaviour of A !100ms B. Currently the timeout starts when A is released, afterwards it should start when it is pressed. Then A !A !100ms B is needed to get the old behaviour.

[houmain]

This is available now in the 3.4.0 release!

[ristomatti]

Curious to test this one! I hope it can still be compiled for Ubuntu 20.02 by disabling Wayland support. 🤞

[ktunprasert]

This is available now in the 3.4.0 release!

@houmain Amazing I will test this out, thank you so much and happy holidays 🎉

[ristomatti]

This is huge!