User Guide

Data Types & Signal Flow
Triggered Data
How it Works
Triggered data only flows through a schematic when an event occurs that ‘triggers’ a change. Until this happens sections of triggered data
remain in a steady state.
When an event does occur a message called a Trigger is sent out through output connectors on one or more components. The trigger flows
through the links until it reaches another component. That component then assesses whether it’s state would be affected. Any necessary
recalculations are then performed and a trigger is sent out through any output connectors on that component. The process continues
creating a waterfall effect through the schematic.
The example below shows a very simple example of two numbers being added together. When you type in a Float component this results in
one of the events that we’ve been talking about and a trigger flurry begins.
Note that during the recalculation part a component may ask the components that provide values to it’s inputs for their latest values. This in
itself can cause a flurry of messages to the left.
What it’s Used For
Triggered data has two main functions. First it provides a way of performing calculations that don’t need to be done at sampling rate. Second
it allows you to build extremely detailed and complex user interface elements which only need to respond when you interact with them.
As a general rule the fast DSP is handled by the Stream data and the slower DSP and user interface is handled by the Triggered data.
Triggered Data Types
The various triggered data types can be grouped into several categories based upon their purpose.
Primary Types
These are the most commonly used types. They represent simple data like numbers and text.
74 of 212