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 and n, also causes the handler to be called.
q+n -> handler called
q n -> handler called
q f n -> handler also called
Is this a limitation of the library, or is there a way to disallow extraneous keys inbetween sequence keys?
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
qandn, 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?