You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very far off and blue sky thinking, but I think it would be cool to allow for multiple action stages to be created and then ordered.
So the UI/UX would be a draggable text interface, something like:
Action Stages
= Every <duration field> press <input field><amount of actions field> times and wait <duration field> before doing it again for a total of <amount of iterations field> times.
= Every <duration field> press <input field><amount of actions field> times and wait <duration field> before doing it again for a total of <amount of iterations field> times.
In which the user could re-arrange the sequence based on their preferred order of execution.
Taking this further, you could even do conditional logic, but I'm not sure what conditions would be useful or if the feature would be at all.
The text was updated successfully, but these errors were encountered:
Ah, that looks like an excellent point of reference! I haven't thought about having the user specify/record their mouse actions or movement yet. I'll add that as another issue.
Very far off and blue sky thinking, but I think it would be cool to allow for multiple action stages to be created and then ordered.
So the UI/UX would be a draggable text interface, something like:
Action Stages
= Every
<duration field>
press<input field>
<amount of actions field>
times and wait<duration field>
before doing it again for a total of<amount of iterations field>
times.= Every
<duration field>
press<input field>
<amount of actions field>
times and wait<duration field>
before doing it again for a total of<amount of iterations field>
times.In which the user could re-arrange the sequence based on their preferred order of execution.
Taking this further, you could even do conditional logic, but I'm not sure what conditions would be useful or if the feature would be at all.
The text was updated successfully, but these errors were encountered: