ProtoFlux:Sequence: Difference between revisions

From Resonite Wiki
cleanup
make consistent with async
 
(One intermediate revision by the same user not shown)
Line 12: Line 12:
|}}
|}}


The '''Sequence''' node performs each of the provided impulses in order, waiting for the [[context]] of each impulse to finish before executing the next one.
The '''Sequence''' node performs each of the provided impulses in order, waiting for the [[synchronous context]] of each impulse to finish before executing the next one.


This can be useful for organizational purposes or to avoid code duplication if something needs to be performed after a bunch of branching paths.
This can be useful for organizational purposes or to avoid code duplication if something needs to be performed after a bunch of branching paths.
Line 20: Line 20:
=== * ([[Impulses|Call]]) ===
=== * ([[Impulses|Call]]) ===


Start the execution of the node.
Start execution of the node.


== Ouputs ==
== Outputs ==


=== Calls (List of [[Impulses|Call]]) ===
=== Calls (List of [[Impulses|Call]]) ===


The list of [[impulses]] to fire in order. The impulses are run in a synchronous [[context]], and after the context of the impulse finishes, the next impulse is fired.
The list of impulses to fire in order. The impulses are run in a synchronous context, and after the context of the impulse finishes, the next impulse is fired.


== Examples ==
== Examples ==
== See Also ==
* [[ProtoFlux:Async Sequence]] for the asynchronous anlogue


[[Category:ProtoFlux:Flow]]
[[Category:ProtoFlux:Flow]]

Latest revision as of 15:20, 13 December 2024

Sequence
*
Calls
+
-
Flow

The Sequence node performs each of the provided impulses in order, waiting for the synchronous context of each impulse to finish before executing the next one.

This can be useful for organizational purposes or to avoid code duplication if something needs to be performed after a bunch of branching paths.

Inputs

* (Call)

Start execution of the node.

Outputs

Calls (List of Call)

The list of impulses to fire in order. The impulses are run in a synchronous context, and after the context of the impulse finishes, the next impulse is fired.

Examples

See Also