Studio

The Config UI builder

Design the settings form players fill in per instance.

A Configurable task has a settings form: the numbers, switches and pickers a player fills in for it on each instance's Task setup. The Config UI builder is where that form is designed, by placing widgets on a live preview. Every field you give a property name becomes a variable the task's flow can read.

123456712345671234567

1. Widgets panel
2. Editing
3. New page (+)
4. Preview form
5. Summary
6. Item on the canvas
7. Properties

1. Widgets panel
2. Editing
3. New page (+)
4. Preview form
5. Summary
6. Item on the canvas
7. Properties

1. Widgets panel
2. Editing
3. New page (+)
4. Preview form
5. Summary
6. Item on the canvas
7. Properties

Set it up

1. In the Task Builder, click Configurable, then open the Config UI tab.
2. Drag Number from Widgets onto the form, or click it.
3. In Properties, set Label to Spins per run and Bind to property to spins; set Min / Max to 1 / 50 and Default to 10.
4. Type a Summary above the form, for example Spins the wheel up to your limit.
5. Click Preview form to check it, then read spins in the Flow tab (pick it from a variable list, or type {spins}).
6. Click Save task. Each instance's Task setup now has a card for the task.

The Widgets panel

Titled Widgets, with the hint Drag onto the form, or click to add. A click adds the widget inside the selected container, just after the selected field, or at the end of the form. Hover a widget to read what it is. A new widget starts with its type as its label and no property name.

Input widgets

Choice widgets

Data widgets

Display widgets

Layout widgets

Templates

Under STRATEGIES and GAME SETUPS, one click drops a ready-made group of ordinary fields. They are yours to rename and rewire, and they do nothing until your flow reads their values.

The canvas

Properties

With nothing selected the panel reads Select an item to edit its label, binding and options. Selecting an item shows its type, what it does and any binding warning, then its properties under GENERAL, BEHAVIOR, DATA and LAYOUT. Hover a property name for help. Remove item deletes it.

Properties most fields share

Properties of common widgets

Container properties

Pages: popups and sheets

A long form can move settings onto extra pages. A page opens from a Popup button on the form, and its fields save into the same task settings as the main form. The New page dialog:

123

1. Page name
2. Shown as
3. Create

Keyboard shortcuts

Click an item on the canvas first, so the builder has the keyboard.

How it works

• Each instance keeps its own values for the form, so one task runs with different settings on every account.
• When the task runs, every field with a property name becomes a variable holding that instance's value, or the field's default when nothing was set.
• A field without a property name is never saved, and a Configurable task with no named field has no Task setup card.
• Templates and task boards only add fields. Nothing changes in the game until the flow reads their values.

Examples

• An optional limit. Toggle Limit spins (property limit_on) and a Number Stop after (property limit) with Visible when limit_on. The flow checks limit_on is true before comparing with limit.
• A fixed header over a scrolling list. A Row with Region header holding the key switches, then a Column with Region body holding the long list.
• Advanced settings out of the way. New page advanced shown as Sheet, rarely-used fields placed on it, and a Popup button Advanced… on the main form with Popup page advanced.

Troubleshooting