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
The following sequence works as expected:
combokeys.bind('q n', function(){ ... })'
However if I bind a combination as well as the sequence:
combokeys.bind(['q+n', 'q n'], function(){ ... })'
or bind the sequence first and then the combination:
combokeys.bind('q+n', function(){ ... })' combokeys.bind('q n', function(){ ... })'
combokeys.bind('q+n', function(){ ... })'
then both the combination and sequence correctly call the handler, but pressing a key inbetween the q and n, also causes the handler to be called.
q
n
q+n -> handler called q n -> handler called q f n -> handler also called
q+n
q n
q f n
Is this a limitation of the library, or is there a way to disallow extraneous keys inbetween sequence keys?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The following sequence works as expected:
combokeys.bind('q n', function(){ ... })'
However if I bind a combination as well as the sequence:
combokeys.bind(['q+n', 'q n'], function(){ ... })'
or bind the sequence first and then the combination:
combokeys.bind('q+n', function(){ ... })'
combokeys.bind('q n', function(){ ... })'
then both the combination and sequence correctly call the handler, but pressing a key inbetween the
q
andn
, also causes the handler to be called.q+n
-> handler calledq n
-> handler calledq f n
-> handler also calledIs this a limitation of the library, or is there a way to disallow extraneous keys inbetween sequence keys?
The text was updated successfully, but these errors were encountered: