Key on hyper layer triggers another layer instead of the layer action

[evan-liu]

Hey, apologies to revive this topic here but I have the opposite problem.

When I am in one layer, I don't want another layer to get activated. All my layers are hyperLayer() and I define them in functions and call them in alphabetical order. I find that the layers first called are the ones that are able to use all alphabetical keys while the layers called after the first layer are unable to use the specific key used to activate the first layer.

For example, I have a yabaiLayer() that is Hyper + Y to activate the layer, then any key press is associated with an action. Before that, I have a raycastLayer() that's activated by Hyper + R.

If I press, Hyper + Y + R, the action associated with R inside yabaiLayer() is never executed, rather raycastLayer() is stacked on top of yabaiLayer().

Originally posted by @kayg04 in #126 (comment)

[evan-liu]

Hi, @kayg04. The original discussion is too long, so I am creating a new one. Can you post the code of one of your hyper-layers? I guess you may have "optional: any" modifiers.

[kaygdotorg]

Hey, here you go: https://stackblitz.com/edit/evan-liu-karabiner-ts-yjiyla?file=rules.js

[kaygdotorg]

I tested it. I cannot trigger number layer from within navigation layer but I can do the opposite so i am guessing it has to do with the order they are defined. Please let me know what you find. Thank you!

[evan-liu]

I've pushed a fix version, 1.30.1. Can you give it a try to see if it solves your problem?

[kaygdotorg]

Yes, it does, thank you so much!

Is there a way I can buy you a coffee or support your work in another way?

[evan-liu]

You are very welcome. I do not have anything set up, but thanks for offering ❤️