At any point in time (even in code other than key shortcut handlers),
you can query the key object for the state of any keys. This
allows easy implementation of things like shift+click handlers. For example,
key.shift is true if the shift key is currently pressed.

At any point in time (even in code other than key shortcut handlers),
you can query the key object for the state of any key. This
is very helpful for game development using a game loop. For example,
key.isPressed(77) is true if the M key is currently pressed.

if(key.isPressed("M"))alert('M key is pressed, can ya believe it!?');

if(key.isPressed(77))alert('M key is pressed, can ya believe it!?');

You can also get these as an array using...

key.getPressedKeyCodes()// returns an array of key codes currently pressed

If you only want some shortcuts to work while in an input element, you can change the scope in the
key.filter function. Here's an example implementation, setting the scope to either 'input' or 'other'.
Don't forget to return true so the any shortcuts get processed.

You can call key.noConflict to remove the key function from global scope and restore whatever key was defined to before Keymaster was loaded. Calling key.noConflict will return the Keymaster key function.