Add option to skip changed signal on an orient event #1056
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.
This change introduces an optional argument to the
orient
function that stops the changed signal from being dispatched.This is necessary where the changed signal would trigger another
orient
in an infinite loop. For example, to synchronise instances over a network, messages can be sent between them by the changed message handler which would trigger anorient
in the other instance. However, thatorient
must not trigger an identical reply, or it will create an infinite loop.