feat(ui): layer behaviour after merging #8428
Open
+71
−26
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.
Summary
A new feature was implemented to refine layer behaviour.
CanvasCompositorModule.mergeByEntityIdentifiers
was modified to defineaddAfter
when the new merged layer is createdrasterLayerAdded
,controlLayerAdded
,rgAdded
andinpaintMaskAdded
were modified incanvasSlice.ts
to add the new layer after the one specified inaddAfter
entityDuplicated
was modified incanvasSlice.ts
to insert the duplicated layer after the original oneuseAddControlLayer
,useAddRasterLayer
,useAddInpaintMask
anduseAddRegionalGuidance
were modified inaddLayerHooks.ts
to insert the merged layer after the selected oneRelated Issues / Discussions
Closes #8002
Checklist
What's New
copy (if doing a release after this PR)