widget 2.0 pickerWheel doesn't soft land, then crashes when values are retrieved

Solar2D Widgets
#1

FYI, all, I’ve opened a bug because you can easily crash the pickerWheel, even in Widget Demo on Windows simulator, just by flicking a wheel up and down a few times until it fails to soft land, then punching Values to blow it up:

in ...corona sdk\sample code\interface\widgetdemo\tab3.lua:121: attempt to index field '?' (a nil value)  

Found out the hard way, when a customer reported it. Assuming getValues() is returning something nil-ish.

Build 1183, so this isn’t some old thing that’s been fixed.

#2

Confirmed: getValues() is returning no values including or after the non-soft-landed wheel. So, if wheel 1 (leftmost) is stuck, getValues() returns {}. If wheel 3 is stuck, getValues() returns { wheel1, wheel2 }.

I’ve worked around it by testing getValues() and informing the user if a wheel is stuck. But considering other bad behavior in pickerWheel (like sometimes stuck wheels return values, but they’re wrong; like asking for values while the wheel is still spinning can return values nowhere close to where the wheel is when getValues() is called), maybe there is a need for significant work in pickerWheel.

#3

Added to the bug list. Will be solved soon.

Alex

#4

Confirmed: getValues() is returning no values including or after the non-soft-landed wheel. So, if wheel 1 (leftmost) is stuck, getValues() returns {}. If wheel 3 is stuck, getValues() returns { wheel1, wheel2 }.

I’ve worked around it by testing getValues() and informing the user if a wheel is stuck. But considering other bad behavior in pickerWheel (like sometimes stuck wheels return values, but they’re wrong; like asking for values while the wheel is still spinning can return values nowhere close to where the wheel is when getValues() is called), maybe there is a need for significant work in pickerWheel.

#5

Added to the bug list. Will be solved soon.

Alex