Allow subclassing AnimatedSwitch and Button #1431
Merged
+2
−2
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.
In order to create a
AnimatedSwitch
which applies thetraitCollection
either a subclass ofAnimatedControl
andreimplementing all the switch logic or creating a wrapper view and
exposing the
AnimatedControl
has to be done.Same is true for
AnimatedButton
.Then use
animatedSwitch.toggle
.Then use
animatedSwitch
directly.Since the public interface of
AnimatedSwitch
ispublic
instead ofopen
functions likefunc setIsOn(_ isOn: Bool, animated: Bool, shouldFireHaptics: Bool = true)
cannot be overridden.Supersedes #1359