-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix gradient chain metadata sync for exposed Fill nodes #4315
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
Draft
YohYamasaki
wants to merge
5
commits into
GraphiteEditor:master
Choose a base branch
from
YohYamasaki:sync-gradient-chain-metadata-for-exposed-fill
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+151
−9
Draft
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
0398eda
Fix gradient chain metadata sync for exposed Fill nodes
YohYamasaki c4d27b8
Avoid using GraphOperationMessage from NodeGraphMessageHandler
YohYamasaki 2b2f603
Avoid transform materialization without gradient edits
YohYamasaki 6893b2e
Add blocker for multi-output custom node
YohYamasaki 6acf3b6
Avoid materializing transform nodes for non-transform gradient updates
YohYamasaki File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Fill or gradient specific functionality should not be inside the generic
NodeGraphMessage::CreateWire. This creates a spaghetti of dependencies. Please write code related to the gradient tool inside the gradient tool.Thanks.
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.
I see, thanks for the comment. I'll find the alternative way.
Uh oh!
There was an error while loading. Please reload this page.
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 your understanding. Hopefully it is clear why I think having seemingly generic node graph changes silently mutate specific graphic nodes is undesirable for maintainability.
Looking at the fill node, it seems the current order of priority appears to be:
List<GradientStops>None) then the bounding box of the layerThe concept of having the hidden inputs to the fill node seems rather confusing. My preferred solution would be to remove these altogether. This would involve the editor tooling setting attributes on the
List<GradientStops>. This simplifies the data model and reduces inconsistencies.However thanks to @Keavon's incomplete refactor (5 months it has had 3 names) it seems that is impossible to set the attributes on a tagged value that get serialized.
An alternative solution the gradient tool read the hidden inputs where appropriate. The gradient tooling should be able to determine if any of the attributes are set (either by traversing the graph looking for known nodes or using the monitor node system). Therefore it can fall back to the fill node inputs. This removes inconsistencies with the tooling and results. However it may sometimes result in confusing behaviour (e.g. if the hidden transform input is set).
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.
I also think the solution you mentioned is the way to go at this moment. Thanks for the detailed explanation.
I think so too, and it was the reason why the hidden input reset was initially implemented in
NodeGraphMessage::CreateWire. But it should be possible to defer this to the interaction point of the tool.