fix double emitting of value_changed event in _on_value_change function #304
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.
Removed a line which caused that value_changed was emitted twice when a vector widget value was changed.
Also fixed a problem that the _value variable of a vector wasn't replaced with a new list when a _NumberValueEdit was changed directly. This caused that the NodeGraph class didn't emit the property_changed signal when changing the number fields of a PropColorPickerRGB widget more than once.
This is because this if condition would be false in these cases:
NodeGraphQt/NodeGraphQt/base/graph.py
Line 257 in 0eb0262
I hope it makes sense, but I can provide more details if needed.