Escape control not working with KR4MB version 8.3.13

[Brian KimJohnson]

Greetings,

This layout looks great but right now the Escape/Control remap is not working

When I type Caps lock (only once) it is mapped correctly but the output to the event viewer is as follows:

eventType:keyMod code:0x3b name:Control_L flags:Ctrl misc:characters: KeyCode::CONTROL_L
eventType:keyMod code:0x3b name:Control_L flags: misc:characters: KeyCode::CONTROL_L
eventType:keyDown code:0x35 name:Escape flags: misc:characters: KeyCode::ESCAPE
eventType:keyUp code:0x35 name:Escape flags: misc:characters: KeyCode::ESCAPE

I tried altering Key Overlaid Modifiers and was able to reduce the keypresses from four to two with Initial Modifier Wait at 10 ms:

eventType:keyDown code:0x35 name:Escape flags: misc:characters: KeyCode::ESCAPE
eventType:keyUp code:0x35 name:Escape flags: misc:characters: KeyCode::ESCAPE

Note that my Modifier timeout is set at 300ms as suggested.

Any ideas?

[Jason Rudolph]

I see the same behavior in the Event Viewer:

Even though the first example (tapping Caps Lock and releasing quickly) causes both Control and Escape to fire, I haven't experienced any practical issues as a result of this.

In my experience, it doesn't matter if the Control key fires in the first example. I tap and release Caps Lock to trigger Escape. It triggers Escape. (Cool.) If it also triggers Control, that has no consequences that I'm aware of. Control is only meaningful (in my experience) when used in combination with other keys (like the last example shows).

Does that make sense? I haven't seen any real world problems as a result of this. If you have, please let me know.

[Brian KimJohnson]

So, I ran through the instructions again and see the multiple key signals
issue.

I am not sure why I see this behavior but this configuration doesn't work
for MacVim or just vim (brew install vim) from command line. When I hit
tab it doesn't bring me out of Insert mode nor does it allow for long-press
behavior.

If you have ideas on how I might test I am open to it but I am not quite
sure what the next step could be. Thanks for your responsiveness - for now
I will just map Caps to one key.

Thanks for your work!

On Mon, Jul 15, 2013 at 8:58 PM, Jason Rudolph [e-mail]:

I see the same behavior in the Event Viewer:

[image: screen shot 2013-07-15 at 8 46 16 pm]https://f.cloud.github.com/assets/2988/801964/9143d13a-edb1-11e2-92a2-02e80d54a95a.png

[image: screen shot 2013-07-15 at 8 48 56 pm]https://f.cloud.github.com/assets/2988/801966/bd57bb38-edb1-11e2-8e27-27e2cb1b7821.png

Even though the first example (tapping Caps Lock and releasing quickly)
causes both Control and Escape to fire, I haven't experienced any
practical issues as a result of this.

In my experience, it doesn't matter if the Control key fires in the first
example. I tap and release Caps Lock to trigger Escape. It triggers Escape.
(Cool.) If it also triggers Control, that has no consequences that I'm
aware of. Control is only meaningful (in my experience) when used in
combination with other keys (like the last example shows).

Does that make sense? I haven't seen any real world problems as a result
of this. If you have, please let me know.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-21014809
.

[Jason Rudolph]

Weird.

Using vim (inside iTerm 2), tapping Caps Lock triggers Escape, and holding Caps Lock enables Control just fine for me. I wish I knew of something that could help you track down the issue.