Difference between revisions of "Fire On Change (LogiX node)"
Jump to navigation
Jump to search
m (null user edge case) |
|||
Line 35: | Line 35: | ||
== Usage == | == Usage == | ||
− | When spawned from the node browser the Value input has an unset dummy data type. This will recast when a valid input is connected. Impulses will only fire for the input user at OnlyForUser and then only when the value changes on that user's instance. | + | When spawned from the node browser the <code>Value</code> input has an unset dummy data type. This will recast when a valid input is connected. Impulses will only fire for the input user at <code>OnlyForUser</code> and then only when the value changes on that user's instance. If the <code>OnlyForUser</code> input is null, the node's active user is null, or the node cannot otherwise deduplicate the impulse via its internal mechanisms, impulses may be fired by multiple users. |
+ | |||
+ | Do not use [[Local_User_(LogiX_node)|Local User]] with this node, it will confuse the deduplication mechanism. Use [[Local_Fire_On_Change`1_(LogiX_node)|Local Fire On Change]] instead. | ||
== Examples == | == Examples == |
Revision as of 03:06, 20 March 2021
The Fire On Change node fires an impulse whenever the input Value changes.
Inputs & Outputs
Color | Label | Type |
Value | dummy | |
OnlyForUser | User |
Color | Label | Type |
Pulse | Impulse |
Usage
When spawned from the node browser the Value
input has an unset dummy data type. This will recast when a valid input is connected. Impulses will only fire for the input user at OnlyForUser
and then only when the value changes on that user's instance. If the OnlyForUser
input is null, the node's active user is null, or the node cannot otherwise deduplicate the impulse via its internal mechanisms, impulses may be fired by multiple users.
Do not use Local User with this node, it will confuse the deduplication mechanism. Use Local Fire On Change instead.