Difference between revisions of "Local Impulse Timeout (LogiX node)"
(Update to new node style & update category) |
|||
(One intermediate revision by the same user not shown) | |||
Line 17: | Line 17: | ||
When an impulse is first received at <code>Trigger</code>, an impulse is fired from <code>Pulse</code> which continues the impulse chain. No further impulses will be fired from <code>Pulse</code>, no matter how many arrive at <code>Trigger</code>. Until either an impulse is received at <code>Reset</code> or a number of seconds has elapsed greater than or equal to <code>TimeoutSeconds</code>. The duration to wait is fixed at the moment that an impulse is fired from <code>Pulse</code>. As such, if the <code>TimeoutSeconds</code> value is changed after the timeout begins, no further impulses will fire from <code>Pulse</code> until enough seconds have elapsed greater than or equal to the previous value of <code>TimeoutSeconds</code> (or an impulse is received at <code>Reset</code>). | When an impulse is first received at <code>Trigger</code>, an impulse is fired from <code>Pulse</code> which continues the impulse chain. No further impulses will be fired from <code>Pulse</code>, no matter how many arrive at <code>Trigger</code>. Until either an impulse is received at <code>Reset</code> or a number of seconds has elapsed greater than or equal to <code>TimeoutSeconds</code>. The duration to wait is fixed at the moment that an impulse is fired from <code>Pulse</code>. As such, if the <code>TimeoutSeconds</code> value is changed after the timeout begins, no further impulses will fire from <code>Pulse</code> until enough seconds have elapsed greater than or equal to the previous value of <code>TimeoutSeconds</code> (or an impulse is received at <code>Reset</code>). | ||
+ | <!--T:6--> | ||
As the node name implies, timeouts and resets are local for each user. Meaning one user may fire an impulse from <code>Pulse</code> and initate a timeout for any impulses owned by them, but another user would be capable of triggering an impulse from <code>Pulse</code> and initating their own timeout immediately afterwards. | As the node name implies, timeouts and resets are local for each user. Meaning one user may fire an impulse from <code>Pulse</code> and initate a timeout for any impulses owned by them, but another user would be capable of triggering an impulse from <code>Pulse</code> and initating their own timeout immediately afterwards. | ||
Line 26: | Line 27: | ||
[[Category:LogiX{{#translation:}}|Local Impulse Timeout]] | [[Category:LogiX{{#translation:}}|Local Impulse Timeout]] | ||
[[Category:LogiX:Flow{{#translation:}}|Local Impulse Timeout]] | [[Category:LogiX:Flow{{#translation:}}|Local Impulse Timeout]] | ||
− | {{:NodeMenu-Flow | + | {{:NodeMenu-Flow}} |
Latest revision as of 14:28, 19 February 2022
Local Impulse Timeout | ||
---|---|---|
Inputs | ||
Impulse | Trigger | |
Impulse | Reset | |
Float | TimeoutSeconds | |
Outputs | ||
Impulse | Pulse |
The Local Impulse Timeout node can be used to filter the rate of impulses passing along an impulse chain.
Usage
When an impulse is first received at Trigger
, an impulse is fired from Pulse
which continues the impulse chain. No further impulses will be fired from Pulse
, no matter how many arrive at Trigger
. Until either an impulse is received at Reset
or a number of seconds has elapsed greater than or equal to TimeoutSeconds
. The duration to wait is fixed at the moment that an impulse is fired from Pulse
. As such, if the TimeoutSeconds
value is changed after the timeout begins, no further impulses will fire from Pulse
until enough seconds have elapsed greater than or equal to the previous value of TimeoutSeconds
(or an impulse is received at Reset
).
As the node name implies, timeouts and resets are local for each user. Meaning one user may fire an impulse from Pulse
and initate a timeout for any impulses owned by them, but another user would be capable of triggering an impulse from Pulse
and initating their own timeout immediately afterwards.