Fixed #732: Content Layers support clone blanks #734
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to #732
This PR allows you to add
CloneBlanks toLayers (cotent layers, specifically), where previously they had to be added toSceneUpdateFragments.This makes the new nested layer system more powerful and useful, as you have less need to pull all the way back up to SUFs for visual requirements that need clones.
As discussed on the issue, I've decided against supporting
SceneAudiohere too, for now. It feels different to clones.While I was here, I also tweaked the way applying magnification works because it was bothering me. There is now a distinction between applying magnification to a single content layer, vs a recursive add to a tree of layers.