We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I spent a few days digging through the code in order to figure out why my sequences were not working properly.
If you are trying to achieve the following scenario, the "g" command always wins.
[ { key: ["g"], command: (output: ShortcutEventOutput) => console.log("g", output), }, { key: ["g a"], command: (output: ShortcutEventOutput) => console.log("g a", output), } ]
If you add a trailing 'space' to to the first command's key, it will be treated as a sequence and the "g a" combination wins.
[ { key: ["g "], // <- Add trailing space here command: (output: ShortcutEventOutput) => console.log("g", output), }, { key: ["g a"], command: (output: ShortcutEventOutput) => console.log("g a", output), } ]
Thanks!
The text was updated successfully, but these errors were encountered:
@abritabroad Are you referring to this? https://github.com/omridevk/ng-keyboard-shortcuts#important-note-1
Sorry, something went wrong.
Yes, there is no mention if needing a trailing space on the single key in order to get the double key's to work.
I think that's more of a bug rather than a feature, i'll need to think about this. but the "g a" sequence suppose to win
No branches or pull requests
I spent a few days digging through the code in order to figure out why my sequences were not working properly.
If you are trying to achieve the following scenario, the "g" command always wins.
If you add a trailing 'space' to to the first command's key, it will be treated as a sequence and the "g a" combination wins.
Thanks!
The text was updated successfully, but these errors were encountered: