Select Data

The Select Data Node.
Because Input Data Sockets in Incari can only receive a value from a single connection, this creates a problem when you wish to converge the Logic into a single branch. This is why the Select Data Node was introduced. The Select Data Node takes two or more pairs of Pulse and Data inputs, and outputs the value corresponding to the input Pulse that the Node was executed by.

The Select Data Node Attributes.
Attribute | Type | Description |
---|---|---|
Data Type | Drop-down | The type of data that will be plugged into the Input Sockets. |
Count | Int | The number of Input Pulses and Data Values the Node will receive. |
Input | Type | Description |
---|---|---|
Pulse [n] | Pulse | The Pulse corresponding to the Data in the Socket below. |
Input [n] | Defined in the Data Type Attribute. | The Data Value corresponding to the above Pulse. |
Output | Type | Description |
---|---|---|
Pulse Output (►) | Pulse | A standard output Pulse, to move onto the next Node along the Logic Branch, once this Node has finished its execution. |
Output | Defined in the Data Type Attribute. | The Data Value received in the Input Socket corresponding to whichever Pulse triggered the execution of the Node. |
The Select Data Node is particularly useful for optimizing our Logic workflow in order to avoid repetition of Nodes. The following example shows how to use the Select Data Node to merge two branches of Logic into a single branch.

The image above shows two branches that have the same effect (modify a Text Object) and could converge into a single branch. For this, the Select Data Node is introduced:

Last modified 4mo ago