-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in CupertinoTimePickerState on Android Emulator #20
Comments
Can you try it without expanding animation? The state of wheel pickers is higly depend on composed content because it is produced by the |
I removed the |
Unfortunately, this is how this picker is designed. You can try different animations such as scale, slide and fade. In such partucilar case scaleIn with TransformOrigin(1f,1f) will probably even look better |
Even with no animation it's broken. I changed the AnimatedVisibility to a simple Also this does not really explain why it's just not working in the Emulator. But until someone discovers this happening on a real device we can close the issue. |
Btw, this picker isn't work as it should on desktop because of the same bug with snapping behavior for trackpad |
Do your emulator and android device both have AM picker? It isn't displayed on your desktop clip. May be the issue is in it? You can set time format manually in the state constructor |
I tried with and without. The bug also happens if I force the 24h format. Is it not reproducible for you? |
I have to report a minor glitch:
For some reason the
CupertinoTimePickerState
changes it values on the first time theCupertinoTimePicker
is shown. It decreases hours and minutes down by one.Interestingly this does not happen on JVM Desktop and it couldn't reproduce it on a real device. As far as I can see this happens only on Android Emulator (running Android 14).
I tried changing locale and timezone, but that did not help.
Maybe you want to see if it could happen on a real device, too.
android_emulator.mov
jvm_desktop.mov
The text was updated successfully, but these errors were encountered: