Handle unordered add / position change events #1555
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.
Fixes (some cases of) plugins ignoring saved
(x, y)
coordinates when aproject is loaded. The canvas can get notified of a plugin's position
before the plugin is actually added, so when the plugin is actually it
just goes to the default position.
This happens because
PatchbayClientPositionChanged
events can arrivebefore
PatchbayClientAdded
events, as seen in debug logs like this:If this happens, the canvas box will be placed in the default position,
rather than obeying the
PatchbayClientPositionChanged
signal. This PRkeeps track of missed events and then applies them once the object is
actually added.