Difference between revisions of "Write (LogiX node)"
m (Zyzyl moved page LogiX: Write to Write (LogiX node): Changing name to match standard form) |
|||
| Line 1: | Line 1: | ||
| − | < | + | <languages></languages> |
| − | [[Category:LogiX: Actions| | + | <translate> |
| + | The '''Write''' node overwrites the referenced Target value with the input Value when an impulse is received. | ||
| + | |||
| + | <!--[[File:|border|256px|right]]--> | ||
| + | |||
| + | == Inputs & Outputs == | ||
| + | {| class="wikitable" | ||
| + | |+Inputs | ||
| + | |- | ||
| + | | Color | ||
| + | | Label | ||
| + | | Type | ||
| + | |- | ||
| + | | style="background-color:{{Impulse-color}}" | | ||
| + | | Write | ||
| + | | Impulse | ||
| + | |- | ||
| + | | style="background-color:{{Dummy-color}}" | | ||
| + | | Value | ||
| + | | (dummy) | ||
| + | |} | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |+Outputs | ||
| + | |- | ||
| + | | Color | ||
| + | | Label | ||
| + | | Type | ||
| + | |- | ||
| + | | style="background-color:{{IValue-color}}" | | ||
| + | | Target | ||
| + | | IValue<nowiki><T></nowiki> | ||
| + | |- | ||
| + | | style="background-color:{{Impulse-color}}" | | ||
| + | | OnDone | ||
| + | | Impulse | ||
| + | |- | ||
| + | | style="background-color:{{Impulse-color}}" | | ||
| + | | 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 == | ||
| + | </translate> | ||
| + | |||
| + | [[Category:LogiX|LogiX]] | ||
| + | [[Category:LogiX: Actions|LogiX: Actions]] | ||
{{:NodeMenu-Actions}} | {{:NodeMenu-Actions}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 08:15, 12 July 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 | ||||