ValuePlug : Disconnection no longer emits plugSet signal #6223
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.
Emitting plugSet signal at that stage was causing issues because the
signal was being triggered before the input was changed, which could
result in incorrect computation during those calls.
Besides,
plugSet
signal is meant to mean "setValue() has been called",and not "getValue() will return something different now" (which is what
plugDirtied
signal is meant to represent).Breaking changes
Checklist