Tapping the "OK" button too fast while UIPickerView is still "animating/rotating" results in the wrong/previous selection. Should delay action/unload?

[benguild]

I've run into this while working a bit too quickly between views before.

If you flick the UIPickerView to a selection, and then it nearly finishes rotating but hasn't 100% finished when you hit "OK", the previous value will still be considered active because the new delegate method hasn't fired before the other callbacks and stuff go through for "OK".

This is a problem with UIPickerView (not this module) in general to be honest... but requires a workaround. It's clear that a selection has been made by the user because it's already settled on a given choice and isn't accelerating fast enough to move past it, but it doesn't account for the fact that there's no reason the user would want the previous selection at that point instead without pressing "Cancel".

Is it possible to get a fix or workaround for this?

[CooperRS]

Hey, I'm aware of that problem. Unfortunately, I do not know of an solution, as UIPickerView as well as UIDatePicker does not tell anyone when the selection has finished (at least as far as I know). Can you help out?

Related: CooperRS/RMDateSelectionViewController#25

[benguild]

OK, I will respond on that issue.