Resolve :data space when deciding whether to connect transformations #4723
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.
Description
Fixes #4722
We have a check which stops transformations from connecting if parent.space != child.space. If the parent is a scene this check looks at the camera and treats
campixel!
as pixel space. This pr adjusts the check to trace back to the scene ifspace == :data
, as that could still be pixel space.In #4722 the text shown in legend is a text plot to a pixel space scene. The linesegments used for LaTeXStrings are hard-coded to be in pixel space. Other elements of the plot are in
space == :data
, which causes transformation to not be connected and thus translations to not propagate to the linesegments.Type of change
Checklist