The Steps editor
The Steps editor has three parts, top to bottom: the step list, the fields of the selected step (open inside the list), and the ADD A STEP chips.
The step list
Each row ① is one step. From left to right a row shows:
- a drag handle, for moving the step;
- its number, counting from 1;
- a bar for each block it sits inside, when it is inside an If or a Repeat block (Conditions, Repeating steps);
- its name, such as Move window to monitor (a rarely used builtin with no plain-language name shows its own name, such as WindowGetClassName);
- a short summary of its fields, such as "Target window, Off". A step that keeps its result ends with "→ $name";
- a warning chip, when there is something to fix.
Otherwise, End if and End repeat rows are markers: they are shown in lighter text and have no fields and no drag handle. When the list has no steps, it says No steps yet. Add one below.
Click a row to select it: its fields open under it ②. Click the selected row again to close it. Only one step is open at a time.
The selected step's fields
The open step shows one field per detail the step needs, labelled in plain words, such as Window or Move the mouse with it. Each field checks what you type as you type it and shows a message under it when something is wrong. Remove at the bottom deletes the step.
Step parameters describes every kind of field.
Adding steps
The ADD A STEP chips ③ add a step just below the selected row, or at the end when no row is selected. Six add the most common steps: Send keys, Type text, Click, Move window, Show a notification and Wait. All N builtins… adds any other step, Set variable stores a value, and If / loop adds a condition or a repeat. See Adding and arranging steps.
Simple mode and Advanced mode
Both modes offer every kind of step and every field, including Save result as. Simple mode hides only what a script writer needs:
Advanced mode. Advanced mode adds:
- The builtin's name at the right of every row, such as
WindowSendToNextScreen. This is the name a script uses. - Signature help under the open step's fields: the builtin as a script would write it, with a sentence on what it does.
- View code at the end of the editor: the steps as text (From Steps to Script).
Expanding the editor
The button at the top-right corner of the block (Expand) makes the editor fill the page, so a long list has room. The Written as switch stays on top. Click the button again (Collapse) or press Esc to return. Leaving the page also collapses it.
Saving
Every change is written into the action as you make it, and counts as an unsaved change in the configuration window until you apply it (The configuration window). A change that can't be written, such as a field that still holds a builtin call, shows Steps not saved: and the reason, and the action keeps its last good steps until you fix it (Problems).