Improve output socket handling of the Value Changed node #2462
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously the "Unchanged" output of the Value Changed node was not activated if the value was unchanged compared to the last value, but only if it was different to the initial value from the first execution of the node. The "Changed" output however compared the last value.
This led to some confusion, so there is now a new output "Is Initial" for the old functionality, and "Unchanged" now checks against the last value as well. It's also possible now to use
null
as a value without always triggering the initialization of the node.