mirror of
https://github.com/node-red/node-red.git
synced 2023-10-10 13:36:53 +02:00
Renamed resetTimeout to restartTimeout
Updated documentation differently
This commit is contained in:
parent
cf2d5841f5
commit
f20565fd16
@ -631,7 +631,7 @@ module.exports = function(RED) {
|
||||
}
|
||||
}
|
||||
|
||||
if (msg.hasOwnProperty("resetTimeout")) {
|
||||
if (msg.hasOwnProperty("restartTimeout")) {
|
||||
if (inflight[partId]) {
|
||||
if (inflight[partId].timeout) {
|
||||
clearTimeout(inflight[partId].timeout);
|
||||
|
@ -115,10 +115,9 @@
|
||||
<p>A <i>count</i> can be set for how many messages should be received before generating the output message.
|
||||
For object outputs, once this count has been reached, the node can be configured to send a message for each subsequent message
|
||||
received.</p>
|
||||
<p>A <i>timeout</i> can be set to trigger sending the new message using whatever has been received so far.</p>
|
||||
<p>A <i>timeout</i> can be set to trigger sending the new message using whatever has been received so far. This timeout can be restarted and set to its initial value by sending a message with the <code>msg.restartTimeout</code> property set.</p>
|
||||
<p>If a message is received with the <code>msg.complete</code> property set, the output message is finalised and sent.
|
||||
This resets any part counts.</p>
|
||||
<p>If a message is received with the <code>msg.resetTimeout</code> property set, the timer for the partly complete message is reset to the original time.
|
||||
<p>If a message is received with the <code>msg.reset</code> property set, the partly complete message is deleted and not sent.
|
||||
This resets any part counts.</p>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user