API

Class FlowGraphReceiveCustomEventBlock

A block that receives a custom event. It saves the event data in the data outputs, based on the provided eventData in the configuration. For example, if the event data is { x: { type: RichTypeNumber }, y: { type: RichTypeNumber } }, the block will have two data outputs: x and y.

Hierarchy (View Summary)

Index

the configuration of the block

dataInputs: FlowGraphDataConnection<any>[]

The data inputs of the block.

dataOutputs: FlowGraphDataConnection<any>[]

The data outputs of the block.

Output connection: The signal that is triggered when the asynchronous execution of this block is done.

An output connection that can be used to signal an error, if the block defines it.

eventRef: FlowGraphDataConnection<string>

Output: the opaque reference identifying the received event source. Receivers configured with the same event id share the same reference, so comparing their event outputs for equality succeeds. The reference format is owned by the host environment.

Input connection: The input signal of the block.

initPriority: number = 1

the priority of initialization of this block. For example, scene start should have a negative priority because it should be initialized last.

metadata: any

Metadata that can be used by the block.

name: string

The name of the block.

Output connection: The signal that is synchronous triggered when the execution of this block is done. Note that is case of events or async you might want to use the done signal instead.

priority: number = 0

The priority of the block. Higher priority blocks will be executed first. Note that priority cannot be change AFTER the block was added as sorting happens when the block is added to the execution queue.

Input connections that activate the block.

signalOutputs: FlowGraphSignalConnection[]

Output connections that can activate downstream blocks.

type: FlowGraphEventType = FlowGraphEventType.NoTrigger

The type of the event

uniqueId: string = ...

A randomly generated GUID for each block.