You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bring CupertinoSwitch up to speed with Switch.adaptive #149275
There are two independent iOS-style switch implementations: Switch.adaptive and CupertinoSwitch.
CupertinoSwitch should support some functionality that Switch has, such as:
Ability to customize mouse cursors.
Ability to customize track outline color and width.
Ability to customize thumb color in both active and inactive states.
Ability to show an image/icon on the thumb.
Ability to resolve properties in different WidgetStates.
Most of these capabilities are already provided via Switch.adaptive on iOS/macOS. However, CupertinoSwitch should also provide these capabilities. This is also an opportunity to bring the Switch and CupertinoSwitch APIs closer together.
Proposal
Part 1
Add these capabilities to CupertinoSwitch.
Part 2
Also, a decision should be made about having Switch.adaptive delegate to CupertinoSwitch so that there are not two independent iOS-style Switch implementations.
changed the title [-]Improve fidelity and customizability of `CupertinoSwitch`[/-][+]Bring `CupertinoSwitch` up to speed with `Switch.adaptive`[/+]on Jul 29, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Roll `Switch.adaptive` changes into `CupertinoSwitch` (#149465)
victorsanni commentedon Jul 25, 2024
Part 1 resolved by #149465.
[-]Improve fidelity and customizability of `CupertinoSwitch`[/-][+]Bring `CupertinoSwitch` up to speed with `Switch.adaptive`[/+]victorsanni commentedon Jul 29, 2024
In order to make this issue more actionable, I will close this issue and create a separate issue for Part 2.
github-actions commentedon Aug 17, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.