PIES Studio 1.9 · Documentation
Every screen, function and event in the PIES Studio editor can be read and changed two ways: drawn, or written as PiLang code. This page covers how you switch between the two and what helps you while you write. The full tour of the editor is in the user manual.
Each editor tab has one view switch in its own toolbar row, at the left, before the palette:
Code is always the option on the right. The selected option is shown as a filled segment, each option has an icon and a label, and its tooltip shows the keyboard shortcut. The tab remembers your choice for that kind of tab, so the next function you open comes up in the view you used last.
Both views edit one draft. A change in Code shows on the canvas or designer when you switch back, and the reverse; nothing is saved until you save the tab, the same as any other edit.
In the dark theme the area around the page in Design, the Canvas and Code are all dark, like the rest of the editor; the page itself keeps your application's own theme colours and has a thin border so you can see its edge. The light theme looks as before.
The Menu & Header designer (Navigation → Menu & Header) has the same zoom control as the screen designer, at its top right: −, the current percentage, + and Fit. It opens fitted to the pane's width, so the whole header shows without scrolling sideways, and refits when you resize the editor; − and + step by 10% between 25% and 200%.
Code is a text editor. Click anywhere and type: one step per line, written as the step's name with its arguments in brackets, such as Create Record(assets, $record, result), and blocks indented by four spaces:
IF ($record.site != "")
Create Record(assets, $record, result)
Return Data($result)
End If
The PiLang reference lists every step and its arguments.
$ values, a table's columns after a dot, operators, and true / false / null. Each suggestion carries an icon for its kind, so a function and a step are told apart at a glance. Enter or Tab accepts, Esc closes.( and after each comma, a hint shows which argument comes next.$ values, operators and comments each have their own colour, in the light and the dark theme.Functions that use Switch, Try or Parallel blocks open read-only in Code; edit those on the Canvas.
On the Canvas each node is titled with the step's name and shows its arguments underneath, such as Create Record over (assets, $record, result) — the same words as its line in Code.
IF ($record.site != ""), Create Record(assets, $record, result) or End If. Selecting a row selects the step on the canvas.PiLang code is the name of a step wherever you edit it. The plain-English sentence for a step appears: