Difference between revisions of "Write Latch (LogiX node)"

From Neos Wiki
Jump to navigation Jump to search
m
(Marked this version for translation)
Line 1: Line 1:
 
<languages></languages>
 
<languages></languages>
 
<translate>
 
<translate>
 +
<!--T:1-->
 
The '''Write Latch''' node overwrites the referenced Target value with the input SetValue or ResetValue when an impulse is received at Set or Reset respectively.
 
The '''Write Latch''' node overwrites the referenced Target value with the input SetValue or ResetValue when an impulse is received at Set or Reset respectively.
  
 +
<!--T:2-->
 
<!--[[File:|border|256px|right]]-->
 
<!--[[File:|border|256px|right]]-->
  
== Inputs & Outputs ==
+
== Inputs & Outputs == <!--T:3-->
 
{| class="wikitable"
 
{| class="wikitable"
 
|+Inputs
 
|+Inputs
Line 30: Line 32:
 
|}
 
|}
  
 +
<!--T:4-->
 
{| class="wikitable"
 
{| class="wikitable"
 
|+Outputs
 
|+Outputs
Line 50: Line 53:
 
|}
 
|}
  
== Usage ==
+
== Usage == <!--T:5-->
 
When spawned from the node browser the Set/ResetValue input has a dummy (or undetermined) type - this will change to match the input data type when a valid input is connected. The SetValue and ResetValue input type, as well as the referenced Target, must match.
 
When spawned from the node browser the Set/ResetValue input has a dummy (or undetermined) type - this will change to match the input data type when a valid input is connected. The SetValue and ResetValue input type, as well as the referenced Target, must match.
  
 +
<!--T:6-->
 
Writing a value with the Write Latch 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 Latch 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:25, 16 September 2020

Other languages:
English • ‎日本語 • ‎한국어

The Write Latch node overwrites the referenced Target value with the input SetValue or ResetValue when an impulse is received at Set or Reset respectively.


Inputs & Outputs

Inputs
Color Label Type
Set Impulse
Reset Impulse
SetValue (dummy)
ResetValue (dummy)
Outputs
Color Label Type
Target IValue<T>
OnSet Impulse
OnReset Impulse

Usage

When spawned from the node browser the Set/ResetValue input has a dummy (or undetermined) type - this will change to match the input data type when a valid input is connected. The SetValue and ResetValue input type, as well as the referenced Target, must match.

Writing a value with the Write Latch 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