I created the following configuration:
https://github.com/KinesisCorporation/Adv360-Pro-ZMK/blob/e1fad2719ca14c0dc6b394e6b3cfcd36c77c492b/config/adv360.keymap
I am using the homerowmods to have easy access to modifiers. [motivation: Homerowmods paired with custom layouts for maxOS and Win enable me to type the special characters of my native language on the Kinesis 360 with relative ease]
When I type fast, letter combinations like l-i will register as Ctrl-i, which is a typing error on my side. However, this is such a common "user-error" that there is a fix for it in the ZMK firmware, the hold-trigger-key-positions feature. This should disable accidental modifier activation on the same hand when typing fast.
Unfortunately, this feature does not work on the firmware built for my Kinesis 360.
It seems the settings on hold-trigger-key-positions are simply ignored.
I created the following configuration:
https://github.com/KinesisCorporation/Adv360-Pro-ZMK/blob/e1fad2719ca14c0dc6b394e6b3cfcd36c77c492b/config/adv360.keymap
I am using the homerowmods to have easy access to modifiers. [motivation: Homerowmods paired with custom layouts for maxOS and Win enable me to type the special characters of my native language on the Kinesis 360 with relative ease]
When I type fast, letter combinations like l-i will register as Ctrl-i, which is a typing error on my side. However, this is such a common "user-error" that there is a fix for it in the ZMK firmware, the hold-trigger-key-positions feature. This should disable accidental modifier activation on the same hand when typing fast.
Unfortunately, this feature does not work on the firmware built for my Kinesis 360.
It seems the settings on hold-trigger-key-positions are simply ignored.