-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable state was not taken into account when pasting a Block #6575
Enable state was not taken into account when pasting a Block #6575
Conversation
Hi! This comment will help you figure out which jobs to run before merging your PR. The suggestions are dynamic based on what files you have changed. VFX Depending on the scope of your PR, you may need to run more jobs than what has been suggested. Please speak to your lead or a Graphics SDET (#devs-graphics-automation) if you are unsure. |
Thanks for the finding, it should be fixed with this commit 5c3ad9b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix; looking solid!
Tested:
Copy/duplicate via right click or keyboard shortcuts on:
- blocks, subgraph blocks
- between different contexts, systems, and VFX assets
- within blocks
- from blocks (copy) to VFX contexts (paste)
- copying/duplicating/creating subgraphs from selections containing disabled and enabled blocks
- undo/redo on all of the above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me but you can probably update the change log to track this resolution.
Thanks 🟢
* Enable state was not taken into account when pasting a Block * Take enabled/disabled state into account when creating subgraphs * Updated changelog # Conflicts: # com.unity.visualeffectgraph/CHANGELOG.md
Purpose of this PR
https://fogbugz.unity3d.com/f/cases/1315482/
Copy paste or duplicate a block in a context would ignore the disable state.
Testing status
Tested:
Comments to reviewers
This is one liner fix, very low risk 😀