Add new CanvasEffect.EffectGraph APIs #517
Merged
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
This PR adds new effect graph APIs to
CanvasEffect
. This enables authors of packaged effects to have a much more compact and safe way to build effect graphs, without the need to suppress nullability warnings when accessing effects from fields nor to manually overrideDispose(bool)
and then dispose every single field, which was pretty error prone as well.API breakdown
Usage example
Here's how the new APIs can be used to define a custom effect, for instance, a "frosted glass" effect. This showcases how the "packaged" effect can build its own internal graph, register nodes, and then reference them when configuring the graph: