Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve output socket handling of the Value Changed node #2462

Merged
merged 1 commit into from
Mar 17, 2022

Conversation

MoritzBrueckner
Copy link
Collaborator

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.

@MoritzBrueckner MoritzBrueckner added the Release Notes: Changes A pull request that is a feature change, not a fix. Used to generate release notes. label Mar 16, 2022
@luboslenco luboslenco merged commit b5bb7e3 into armory3d:master Mar 17, 2022
@MoritzBrueckner MoritzBrueckner deleted the value-changed-node branch March 17, 2022 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release Notes: Changes A pull request that is a feature change, not a fix. Used to generate release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants