Allow recipes to read keyboard, mouse buttons, mouse position, etc.
|Opened on:||Tuesday, May 15, 2012 - 04:45|
|Last modified:||Wednesday, May 16, 2012 - 00:25|
Let recipes follow user behavior as they run, for example,
reading the keyboard or responding to mouse clicks, double-clicks, press-and-holds, positions, or motions.
With commands like these, much more interactive recipes could be made.
For example, the user could do things like sketch on the screen how they want a protein to fold.
The user could also trace a path for the protein segments to follow.
A recipe could vary the value of some parameter every time an up or down arrow is clicked.
A recipe could break out of certain loops when the space bar is pressed.
Such commands would allow more versatility than dialog boxes do,
and they wouldn't force a recipe's operations to stop every time they might benefit from human input.
Reading the keyboard would let a recipe run on auto-pilot until a user chooses to intervene.