Picker Wheel will not allow selection

Solar2D Widgets
#21

I fully agree with your sentiments on the time it has taken to resolve these issues. 1.5 years to get something stable, which originally was released because Widgets 1, in Walter’s words, was “embarrassing” is simply double-embarrassing. However, it is what it is and the only choice clearly left to us to consider is to move on and not use Corona SDK at all. With all the lobbying and complaining this is the best we got. 

I think the Widgets 2 is now stable enough to consider (at least for me) but the problem here is probably the G1 compatibility mode. I saw on day 1 that this mode would not be well supported and issues fixed in G2 native mode would not necessarily be fixed in G1 mode simply because not as many people are using it and reporting bugs etc. Moving on from G1 compatibility mode will make a big improvement on your Widgets 2 experience. Highly recommended. 

Good luck with your project.

#22

Unfortunately we have not been able to do so for other various reasons. Until we find a good solution for our group-nesting problem which we reported a few months ago and others have had the same issue, this thread: http://forums.coronalabs.com/topic/46954-solution-to-fix-nested-groups-in-g20/ we wont be able to fully migrate properly since our apps are still heavily depended on the old previous group G1.0 behaviors. But thanks for the tip nevertheless  :slight_smile:

#23

I know exactly where you are. Been there a few times where I needed to go forward to ‘enjoy’ some fixes to some components but could not due to other bugs or issues introduced along the way. Very tough place to be especially when you have deadlines to deal with as well. IMHO, the whole post G2 stabilization era is not over yet. Almost a year over that and we are still dealing with the massive transition G1 to G2 proved to be. The upcoming changes, ie Windows Phone support etc scare me even more. Lets hope for the best.

#24

Hi @mslack,

My advice would be, don’t use a pickerWheel for just 3 pieces of data in one column. IMHO, that is “overkill” from the UI standpoint, making the user manipulate a wheel just to select a skill level. I would suggest a radio button set, or even a tabBar or segmentedControl. Just 3 pieces of data in a picker is not designed to work properly, as there just isn’t much data to scroll up and down.

Best regards,

Brent

#25

Yea well that is just an example.  I use the picker wheel for variable sets of options.  Just noticed that if the set is short like this it is broken.  So saying do something else is not really an option as i don’t control the number of options that are being selected from.

So this is a bug?

Should it be fixed?

#26

Hi @mslack,

Yes, this appears to be a bug, if you can’t select the proper item. Can you compile a quick test case and submit it as a bug report?

Thanks,

Brent

#27

The code above is the test … bug report submitted

#28

Yes this is a bug. It was working well with 3 entries before 2282. I also reported this as 

(Case 32337) PickerWheel with few entries has major alignment problem - Regression bug in  2282

Hope it will get fixed very soon. 

#29

Agreed … bugs like this are likely easy to fix but at the same time keep us from being able to move forward in the Corona Codebase which fixes all kinds of issues.

Please get this fixed.

Cheers

#30

I need the other widget fixes delivered in 2282 but can’t go there because of this particular bug which ironically 2282 introduced… Oh and another one introduced in 2276 to the mapView. Both are regression bugs and are supposed to get the highest priority so I keep fingers crossed and wait. To CL’s credit though, it does appear that we are getting more timely and regular fixes to these issues of late. It still doesn’t help that there are so many issues that need to be fixed though.

#31

Any comment from Corona on fixing this regression bug?

#32

I am holding back a release just because of this bug. I wish a small incremental bug fix sorting just this one would be made available. The current approach of fixing many widget issues and releasing one big batch every 2 to 3 months is not always the best way to go. 

#33

Still no comment from Corona! … When might we see these bugs fixed.  We really need better regression testing prior to checking in code changes … IMO

#34

This fix is currently in testing and should be released soon, but I do not have a specific ETA or build number.

#35

Thanks for all the efforts in making the widgets much more robust and feature complete. The recent bug fixes + skinning abilities are all very much appreciated. Thanks

#36

Thanks for the ack that this is being handled … appreciate the feedback!  Testing good …  :)

#37

Any updates on this? I’m still experiencing this issue with 2014.2322.

http://cl.ly/3K3G3o183V0w

#38

Try Daily Build 2332. The contents page say nothing about the widget fixes that went in but it does appear that some bug fixes were included in that daily build. My pickerWheel finally works well with just 3, 4 entries in it. Corona Labs, thanks much for making this happen. :slight_smile:

#39

Build 2332 contained a whole host of widget fixes but I don’t have a complete list.  There were several pickerWheel bugs, skinning bugs and such fixed.

Rob

#40

thanks for the update.

It would be nice if these were documented in the notes … helps us greatly when we are trying to use daily builds if the developers use good notes on their checkins.  Please to impress upon them that this is an important part of the corona eco system.