|
I think for some tasks a ticking script would work better and be simpler to use, for some the triggering you describe. Wouldn't hurt to have both IMHO.
"Change Set: KeystrokeScriptInstatiation
Date: 6 February 2010 Author: Karl Ramberg Enables the #keyStroke script instatiation with global scope. Scripts trigger on event #keyStroke and do not need to be ticking. You still need to test for which key that was hit to differentiate different behaviour. Also the scripts do not run continously. For this to work smoother, and pick up different keystrokes simultanously deeper hacking is needed" "Change Set: KeystrokeScriptInstatiation
Date: 13 February 2010 Author: Karl Ramberg Enables the #keyStroke #keyDown and #keyUp script instatiation with global scope. Scripts trigger on event #keyStroke #keyDown and #keyUp and do not need to be ticking. You still need to test for which key that was hit to differentiate different behaviour. Also the scripts do not run continously. For this to work smoother, and pick up different keystrokes simultanously deeper hacking is needed" |
|||||||||||||||||||||||||||||||||||||||
Then you could trigger scrips without dealing with a ticking test script looking for different keys and maybe we could get better response time as well