We’ve released KMP Wheel Picker, which provides a ...

# feed

[Patrick Michalik]

We’ve released KMP Wheel Picker, which provides a modular wheel picker for Compose Multiplatform:

• Use your own composables for the items and window.
• Style items based on position.
• Customize the buffer size, animations, and scroll friction.
• Scroll programmatically with an animation.
It’s compatible with iOS, Android, and desktop. Check it out on GitHub.

kmp-wheel-picker.mp4

[Michael Paus]

And why doesn't it support the other relevant platforms too? As all your code is in commonMain already, this shouldn't be too difficult.

[Patrick Michalik]

We started with iOS, Android, and desktop because those are the three platforms where Kotlin Multiplatform is the most established. We’ll be looking into adding web support too!

[Stefan Oltmann]

You likely may not need to do anything else than just adding the target.

[Stefan Oltmann]

Personally I would try to add all targets I can to cover it all.

[Marek Kaput]

I will defend our position because it's not just adding a new target. In general, one needs to at least test it thoroughly and make some samples 😉 But to be specific, we will keep this request in mind; it's a matter of priorities. PRs are also welcome!

[nkiesel]

Would be nice to see a time selector example using the wheel picker for hours and minutes. This then should also allow to scroll from e.g. 15:05 to 14:55 by scrolling the minutes down by 10 minutes.

[Stefan Oltmann]

Not fixed 10 minutes, but a configurable stepping.

[Patrick Michalik]

Thanks for the idea! We’ll look into it. We’ve opened issues for both suggestions.

[nkiesel]

I did not meant to have 10 minute steps. I meant to have 1 minute steps but when scrolling minutes by a full hour to also adjust the hour. So if starting at 15:05 and scrolling the minutes 5 times, will be at 15:00 and then when scrolling one more minute the result should be 14:59.

[Stefan Oltmann]

Makes sense, but should be optional as many pickers don’t behave like that - so it might confuse some users that are not used to that.

[nkiesel]

Yeah, clearly should be configurable if scrollers affect other scrollers, and also whether when reaching the end of the value range it should be really an end or connecting to the other end of the range.