fix sub title |
overhaul |
||
| Line 14: | Line 14: | ||
|}} | |}} | ||
The '''Start Async Task''' node starts a new nested [[async context]] at the current impulse. | |||
== Inputs == | == Inputs == | ||
=== * ([[Impulses|Call]]) === | === * ([[Impulses|Call]]) === | ||
Start | Start the async task. | ||
== Outputs == | == Outputs == | ||
| Line 27: | Line 26: | ||
=== TaskStart ([[Impulses#ASync|AsyncResumption]]) === | === TaskStart ([[Impulses#ASync|AsyncResumption]]) === | ||
The new async context made by the node. This impulse chain will run until it encounters any sort of asyncronous delay, at which it will continue execution along the <code>OnStarted</code> chain. | |||
This context is ''nested'', meaning that any context-specific things, such as [[ProtoFlux:Local Value|locals]], are duplicated from the context that <code>*</code> comes from. Any future changes to context-specific things will not be reflected in the <code>OnStarted</code> chain and vice versa. | |||
=== OnStarted ([[Impulses|Continuation]]) === | === OnStarted ([[Impulses|Continuation]]) === | ||
Fires at the | Fires once <code>TaskStart</code> encounters any sort of delay, effectively running at the same time given the now-separate contexts. | ||
=== OnFailed ([[Impulses|Continuation]]) === | === OnFailed ([[Impulses|Continuation]]) === | ||
Fires | Fires if the task was unable to be started. Currently, this only fires if <code>TaskStart</code> is not connected to any node. | ||
< | |||
</ | |||
[[Category:ProtoFlux:Flow:Async]] | [[Category:ProtoFlux:Flow:Async]] | ||
Revision as of 19:59, 15 December 2024
The Start Async Task node starts a new nested async context at the current impulse.
Inputs
* (Call)
Start the async task.
Outputs
TaskStart (AsyncResumption)
The new async context made by the node. This impulse chain will run until it encounters any sort of asyncronous delay, at which it will continue execution along the OnStarted chain.
This context is nested, meaning that any context-specific things, such as locals, are duplicated from the context that * comes from. Any future changes to context-specific things will not be reflected in the OnStarted chain and vice versa.
OnStarted (Continuation)
Fires once TaskStart encounters any sort of delay, effectively running at the same time given the now-separate contexts.
OnFailed (Continuation)
Fires if the task was unable to be started. Currently, this only fires if TaskStart is not connected to any node.