Actions

Actions are used to send commands from Ctrl Engine. Actions can send multiple commands simultaneously or at differing time offsets using their inbuilt timeline.

Multiple Actions can be trigged at the same time within a Ctrl Suite workspace.

Timelines

Once an Action is triggered, its timeline begins playing back. By default, all Actions are set to trigger instantly (all at 00:00:00).

To stagger Actions, use the timeline UI to drag & drop each action to give a precise start time.

Note: Actions have been created to offset triggering of events as opposed to creating long format timelines playback schedules.

Triggering Actions

Nodes view

Within the nodes view of Ctrl Designer, any Action's output can be tested by pressing its Play icon when connected to Ctrl Engine.

Interfaces

Within interfaces select a UI component (i.e. a button). Under its Protocol options select Action then use the dropdown to navigate to the Action(s) to be triggered when the button is interacted with.

Processes

Each Action's timeline can be played, paused, stopped and restarted using the Action blocks that auto-populate within all Processes once they are created.

Action blocks allow three inputs (Play, Pause & Stop), each performing their function when receiving input from another process block. (i.e. the output of logic, an event timer or more).

Once an Action completes playback, it auto-resets, ready to be played again.

If the Play, Pause or Stop inputs are triggered when their function is already active, the trigger is ignored.