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
Add selectionOverlay parameter to CupertinoTimerPicker #68509
changed the title [-]Add to CupertinoTimerPicker selectionOverlay paramater[/-][+]Add to CupertinoTimerPicker selectionOverlay parameter[/+]on Oct 19, 2020
changed the title [-]Add to CupertinoTimerPicker selectionOverlay parameter[/-][+]Add selectionOverlay parameter to CupertinoTimerPicker [/+]on Oct 20, 2020
CupertinoDatePicker doesn't have optional param for selectionOverlay Widget, so it can't be overridden or changed.
This class should have the same option as CupertinoPicker, so we can change this overlay widget.
I think the right design for this would be to not add Widget selectionOverlay to either CupertinoTimePicker or CupertinoDateTimePicker, or any other "Picker".
Instead I propose to add pickerSelectionColor to CupertinoTheme (defaulting to CupertinoColors.tertiarySystemFill), and the CupertinoPickerDefaultSelectionOverlay used underneath CupertinoPicker, defaults to CupertinoTheme.pickerSelectionColor.
Reacted by Bohdan Honcharuk
Reacted by Ermek Akmatov, keyurtailor44, Gufdoor and JiaheEatingOut
Are there any updates on this? Looking at the source code it should be a rather straightforward fix, and It would be much appreciated in many Cupertino-based projects.
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
[-]Add to CupertinoTimerPicker selectionOverlay paramater[/-][+]Add to CupertinoTimerPicker selectionOverlay parameter[/+][-]Add to CupertinoTimerPicker selectionOverlay parameter[/-][+]Add selectionOverlay parameter to CupertinoTimerPicker [/+]DanielEdrisian commentedon Oct 30, 2020
@sanekyy Can you provide more context on this issue?
sanekyy commentedon Oct 30, 2020
I can't provide selectionOverlay to CupertinoTimerPicker to override default value of this parameter.
I want customize it, but I can't with current api.
lecicdjuro commentedon Apr 1, 2021
CupertinoDatePicker doesn't have optional param for selectionOverlay Widget, so it can't be overridden or changed.
This class should have the same option as CupertinoPicker, so we can change this overlay widget.
@DanielEdrisian I'm using the latest stable version
[✓] Flutter (Channel stable, 2.0.3, on macOS 11.2.3 20D91 darwin-x64, locale en-RS)
• Flutter version 2.0.3 at /Users/lecicdjuro/flutter
• Framework revision 4d7946a (2 weeks ago), 2021-03-18 17:24:33 -0700
• Engine revision 3459eb2
• Dart version 2.12.2
daadu commentedon May 18, 2021
I think the right design for this would be to not add
Widget selectionOverlayto eitherCupertinoTimePickerorCupertinoDateTimePicker, or any other "Picker".Instead I propose to add
pickerSelectionColortoCupertinoTheme(defaulting toCupertinoColors.tertiarySystemFill), and theCupertinoPickerDefaultSelectionOverlayused underneathCupertinoPicker, defaults toCupertinoTheme.pickerSelectionColor.TetrixGauss commentedon Jul 8, 2022
what is going on with that update????
binSaed commentedon Oct 6, 2022
Any update? or everything in flutter we need to rebuild from scratch!
6 remaining items
Requieem commentedon Jan 25, 2024
Are there any updates on this? Looking at the source code it should be a rather straightforward fix, and It would be much appreciated in many Cupertino-based projects.
flutter-triage-bot commentedon Mar 30, 2024
This issue is missing a priority label. Please set a priority label when adding the
triaged-designlabel.HansMuller commentedon Apr 3, 2024
A fix appears to be underway - #143079
MitchellGoodwin commentedon Jul 12, 2024
Fixed as a part of #143079
github-actions commentedon Jul 26, 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.