Alex can you kindly post the list of recent updates that went live in 2332 and 2338? Thank you so much for your hard work and continued efforts.
Yep, if anyone from Corona could address this, I’d be much obliged as well. What does “Update widget to latest” mean. for instance?
Hey guys,
2332 and 2338 contain:
31768 - widget.newSegmentedControl() – segments not highlighting properly
31769 - widget.newSegmentedControl() – divider frame broken and dysfunctional
31772 - widget.newSlider() – handle width/height not respected.
31773 - widget.newSlider() – fill parameters missing or not respected.
31914 - widget.newPickerWheel() – column items mis-aligned if optional “align” property is not specified.
31761 - widget.newPickerWheel() – custom skinning frame offset issue
31762 - widget.newPickerWheel() – labels colors not highlighting properly.
31763 - widget.newPickerWheel() – can’t select the final option in any column.
31764 - widget.newPickerWheel() – fontColor is non-functional
31770 - widget.newSegmentedControl() – labelColor 'over’ dysfunctional
30390 - SetFillColor not working on widget button
29143 - obj:setValue() method is not yet implemented for newSegmentedControl() (I added object:setActiveSegment(segmentNum) for this)
32337 - PickerWheel with few entries has major alignment problem - Regression bug in 2282
Thanks,
alex
Alex, this is a great list! Thanks much for your continued hard work.
Question, given all the fixes we see listed above for the segmentedControl are we now at a point where we can skin this thing? Will there be an update to the API pages showing us how to change the visuals of a segmentedControl soon?
Looking forward to more of your good work and Brent’s updates on the API pages. Thank you very much!!!
Sure thing. One mention though, Brent and Rob had a huge contribution to the last two widget fixes batches. So with your permission, Kerem, i’ll redirect your thanks to them as well.
Thanks,
alex
Absolutely, I didn’t know or otherwise I would be the first to say thanks. So lets correct that now!
Rob, Brent, thank you very much for your continued support and help in getting these widget fixes out. Most appreciated.
You’re welcome all. The (daily) docs are now fully updated with skinning details for all widgets, and visual examples of how it should be done:
http://docs.coronalabs.com/daily/api/library/widget/index.html
I know this took much longer than expected and I appreciate your patience. As usual, if you find any glaring issues, please isolate test cases and file them as bugs so that we may investigate and fix them.
Thanks,
Brent
P.S. - I noticed one broken link in newSegmentedControl() for the “:setActiveSegment()” method. This is just formatting issue which I’ll fix right away… the method should still work fine (just provide a valid segment number as the sole argument to the method).
Best news ever!!! So it is true? I can skin a segmentedControl now? I will try this right away!!! Thank you very much guys. This made my day.
Yup, the :setActiveSegment() method works great! Already tested and its used in a released app. Great going.!
Im sorry to disturb the Celebration.
I was so happy to hear that the PickerWheel finally should work.
Download latest NightBuild: 2340
and tested the Pickerwheel.
Does nobody else see that after u created a simple pickerwheel,
(for example: just with one column and lets say 50 Rows of numbers 1-50)
and u scroll up/down fast… it seems it will stop soon… than it makes a big jump und goes 4 Rows further to stop.
When u scroll up its even worse, u cant exactly stop above a number. It will also jump suddently 3 Rows further to stop.
Result: PICKERWHEEL still buggy and not fixed 
Unusable…
in the Simulator when u scroll to the first Row… and than strongly move down… the numbers jump from centered to left aligned in a mix.
Better luck, next time.
Greets
Chris
For me it is past a point where I can live with the remaining issues while hopefully they get tackled one by one soon as well. I know it will never be perfect or match 100% the native UI elements but they are good enough & close enough for what I need them to do for me. I know there is ways to go but IMHO, the light at the end of the tunnel is getting stronger by the day.
just to give an example.
its not about to be a 100% native ui for me… instead just a working one 
here a video… hope that makes it more clear and is helpful to track the bug
We were glad to help.
These are exactly the issues we are experiencing as well which make the picker wheels unusable for us. We have a critical update that we absolutely MUST get out asap but this little annoyance among some other things are holding us back from submitting it. Would be nice to see a fix for this ASAP.
By the way curious, are you using graphicsCompatibility mode 1 as well? Or is this an issue with both graphics versions?
Edit: Attached a video of our pickerWheel as well just to demonstrate how much it currently works.
Sorry to hear you are still having these problems. One question. I noticed the videos are from Simulator. Do you also see similar issues on device builds? Please try without G1 compatibility mode and see if the issues go away. I see nothing like this in the pickerWheel implementation now but I don’t use G1 compatibility mode. Maybe thats the key to the remaining issues. Good luck!
Yeah tried them both on the device and the simulator but getting the issues on both. Suspecting it to be a G1.0 compatibility issue but afaik G1.0 isn’t deprecated yet? So you’d hope it to work properly on both
The main issue is that there is very little resource allocated to dealing with these bugs. As far as I know, and I might be wrong, its just one person who is also responsible for other parts of Corona SDK so we’re getting a fraction of an FTE time on these issues. Solid progress is made and for that I am very thankful but as you are finding out, we are far from being totally out of this mess yet.
My hunch and again, I might be totally wrong is that the widgets are not stress tested in G1 compatibility mode simply because there aren’t that many people using G1 compatibility and the widgets.This possibly results in having some bugs persist while they are fixed in G2. Again, just a hunch of course.
The more people are affected and make a noise about these issues the more likely the issue is to get attention. Look at @guruk’s video for example. It has been downloaded a total of 10 times and I think 2 of those downloads was me… What he demonstrates there is pretty serious. I totally agree with him in that it is unusable in the state that he demonstrates the widget. I don’t see that behavior in my app but he does. Unless followed up with a bug report with code etc it is unlikely CL engineers will be able to duplicate it and fix it either.
So in a nutshell, we need bug reports, sample code and visibility, lots of visibility.
Hey guys,
Please file a bug and paste back the number. Even if on g1 compat, it sounds like a serious issue and will be treated accordingly.
Thanks in advance,
alex
Hey Alex,
Thanks much for being here for us even on your Sunday. Your support is most appreciated.
Regards,
Kerem
Very much so! Will go ahead and file one as soon as I get home.
Thanks again//
hi… yes i also use G1 compatibility mode…
also again im on travel and less time… feel free to add my video to the Bug List.
I guess there u see very clear the problem…
and yes… stress it out to test with G1 Mode
Thanks
Greets
Chris