Allow recipes to read keyboard, mouse buttons, mouse position, etc.
| Case number: | 845813-992669 |
| Topic: | Game: Tools |
| Opened by: | jeff101 |
| Status: | Duplicate |
| Assigned: | Anonymous |
| Priority: | 3 |
| Type: | Feature |
| 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.
Who has the ability to make any changes to Foldit? Do you? If my suggestions have already been made many times before, they must be popular ideas. Why have they not already been acted upon? How long does it typically take for apparently popular ideas to get implemented? Please direct me to where they were previously suggested so that I can add my vote to the previous suggestion and raise its priority some. Help me join the chorus.
Right next to the submit feedback button is the search field. You just type 'pause' into that and you get *EIGHT* feedbacks (in ALL category), one of which has 36 upvotes, and is only from February.
The dev team's priorities are to make sure the very basic tools are working correctly: wiggle, shake, rebuild, mutate, alignment. Rebuild still doesn't work right. David Baker thinks improving the alignment tool is the key to doing better on CASP puzzles than we did 2 years ago.
He's a forum post called a Christmas list http://fold.it/portal/node/992324 . It's a Christmas list because a) it's wishful thinking, and b) it might get worked on by Christmas..2013.
Nothing that changes how Foldit does anything is going to get worked on until CASP is over. They don't want to introduce a bug that will take 2+ weeks to get noticed and ruin 2+ weeks of contest entries.
Foldit is 4 years old and some features have simply been abandoned or replaced. The person who wrote the Selection Interface doesn't even work there any more. GUI scripts have limitations, yes, that's why Lua was included. That had limitations, and that's why it was redesigned into Lua v2. This took YEARS.
http://fold.it/portal/node/992324 suggests reading the keyboard, among other things.
| Status: Open » Duplicate |
We can use xpcall in LUA v2 scripts. Adding dialog boxes there is possible - you can break script pressing esc or "stop" button, script can catch this and continue after some changes.
See there:
http://fold.it/portal/node/991496#comment-16717
Marking as duplicate to:
http://fold.it/portal/node/986021
I will try the suggestion about xpcall. Thanks Rav!
![](http://128.95.1.228:8000/tracking_pixel.gif?events=scAdd&f=1111&wdata={"x":12, "y":11}){kind=tracking}
again - suggestion for pausing scripts have been requested many times before - please read previous posts and collate