Difference between revisions of "Write (LogiX node)"
(Marked this version for translation) |
|||
| Line 1: | Line 1: | ||
<languages></languages> | <languages></languages> | ||
<translate> | <translate> | ||
| + | <!--T:1--> | ||
The '''Write''' node overwrites the referenced Target value with the input Value when an impulse is received. | The '''Write''' node overwrites the referenced Target value with the input Value when an impulse is received. | ||
| + | <!--T:2--> | ||
<!--[[File:|border|256px|right]]--> | <!--[[File:|border|256px|right]]--> | ||
| − | == Inputs & Outputs == | + | == Inputs & Outputs == <!--T:3--> |
{| class="wikitable" | {| class="wikitable" | ||
|+Inputs | |+Inputs | ||
| Line 22: | Line 24: | ||
|} | |} | ||
| + | <!--T:4--> | ||
{| class="wikitable" | {| class="wikitable" | ||
|+Outputs | |+Outputs | ||
| Line 42: | Line 45: | ||
|} | |} | ||
| − | == Usage == | + | == Usage == <!--T:5--> |
When spawned from the node browser the Value input has a dummy (or undetermined) type - this will change to match the input data type when a valid input is connected. The input type and that of the referenced Target must match. | When spawned from the node browser the Value input has a dummy (or undetermined) type - this will change to match the input data type when a valid input is connected. The input type and that of the referenced Target must match. | ||
| + | <!--T:6--> | ||
Writing a value with the Write node synchronizes the value across all users in a world. Hence each time this node operates some information must be passed over the network between users. Typically this is negligible (unless writing absolutely huge strings). However, if a large number of writes are occurring it can incur significant network load which may result in lag. If a LogiX setup requires a value to be changing very rapidly and/or continuously, consider driving it directly rather than writing every new value. | Writing a value with the Write node synchronizes the value across all users in a world. Hence each time this node operates some information must be passed over the network between users. Typically this is negligible (unless writing absolutely huge strings). However, if a large number of writes are occurring it can incur significant network load which may result in lag. If a LogiX setup requires a value to be changing very rapidly and/or continuously, consider driving it directly rather than writing every new value. | ||
| − | == Examples == | + | == Examples == <!--T:7--> |
| − | == Node Menu == | + | == Node Menu == <!--T:8--> |
</translate> | </translate> | ||
Revision as of 20:18, 16 September 2020
The Write node overwrites the referenced Target value with the input Value when an impulse is received.
Inputs & Outputs
| Color | Label | Type |
| Write | Impulse | |
| Value | (dummy) |
| Color | Label | Type |
| Target | IValue<T> | |
| OnDone | Impulse | |
| OnFail | Impulse |
Usage
When spawned from the node browser the Value input has a dummy (or undetermined) type - this will change to match the input data type when a valid input is connected. The input type and that of the referenced Target must match.
Writing a value with the Write node synchronizes the value across all users in a world. Hence each time this node operates some information must be passed over the network between users. Typically this is negligible (unless writing absolutely huge strings). However, if a large number of writes are occurring it can incur significant network load which may result in lag. If a LogiX setup requires a value to be changing very rapidly and/or continuously, consider driving it directly rather than writing every new value.
Examples
Node Menu
| Actions | ||||||
|---|---|---|---|---|---|---|
| Back | -- | ++ | Drive | Drive Playback | Tween | Write |
| Write Latch | Write Ref | Write Ref Latch | ||||