Simple Counter:
Simple Counter is a utility node that passes a whole-number value through for use elsewhere in your workflow. Despite its name, the implementation does not increase a number, track progress, or maintain a running total. It is useful when you need to supply a chosen integer to another node. The node also signals that its result has changed whenever change detection is checked, so you should not rely on it being treated as unchanged between evaluations.
Simple Counter Input Parameters:
start
A whole-number input with a default of 0, a minimum of 0, and a step size of 1; no maximum is specified in the source. Although you can set this value, the current implementation does not use it to calculate the result. Changing start alone therefore does not change the value produced by the node.
count
A whole-number input with a default of 0, a minimum of 0, and a step size of 1; no maximum is specified in the source. This is the value the node passes through unchanged. For example, setting count to 5 produces 5, regardless of the value set for start.
Simple Counter Output Parameters:
index
A whole-number value equal to count. You can connect index to another node that accepts an integer. The name does not imply an automatically advancing position: this node does not add to, subtract from, or otherwise calculate the value.
Simple Counter Usage Tips:
- Set
countto the exact integer you want to send onward; leavestartat its default unless you have another reason to set it, because it does not affectindex. - Connect
indexto an input that accepts an integer. To produce a changing sequence, use another part of your workflow to provide changing values tocount; this node does not advance them itself. - Use nonnegative whole numbers when entering values in the node’s controls, which specify a minimum of 0 and increments of 1.
Simple Counter Common Errors and Solutions:
No node-specific error messages are defined
- Explanation: The provided class contains no explicit error messages or exception handling. The examples below describe possible validation or workflow problems, not messages guaranteed to appear verbatim.
- Solution: If an error appears, check the exact message shown by your application and confirm the connected values and sockets.
Invalid value for start or count
- Explanation: The node declares both inputs as integers with a minimum of 0. An application may reject a negative, fractional, or nonnumeric value during input validation; the exact error wording is not defined here.
- Solution: Enter a nonnegative whole number for each input.
Missing required input: start or count
- Explanation: Both inputs are declared required. Depending on how your application handles node controls and connections, removing or supplying an invalid value may prevent execution; the class does not define a specific message.
- Solution: Ensure both inputs have valid integer values. Their default values are 0.
start changes, but index stays the same
- Explanation: This is expected behavior, not an execution error. The node returns
countdirectly and does not usestartin its result. - Solution: Change
countto changeindex. Use a different node or workflow step if you need the starting value to affect a calculation.
index does not increase automatically
- Explanation: This node stores no running counter and performs no increment. It returns the current
countvalue each time it runs. - Solution: Provide changing values to
countfrom elsewhere in your workflow if you need an advancing index.
