Refactoring for VisualEffect class #679
Draft
Conversation
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
chrisbanes
force-pushed
the
cb/visualeffect
branch
5 times, most recently
from
a254435 to
98ce376
Compare
chrisbanes
force-pushed
the
cb/visualeffect
branch
4 times, most recently
from
97beeaf to
29b6df7
Compare
chrisbanes
force-pushed
the
cb/visualeffect
branch
from
29b6df7 to
794bbd5
Compare
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.
This is the first step towards v2.0
All of the blurring logic is now encapsulated into a
BlurVisualEffectclass, paving the way for Haze to exposeVisualEffectas a public API for custom effects. Still a while until we get there, but this is a big first step.