Hello Rob,
Thanks for the prompt response!
We went ahead and tried with 2014.2162, and are still experiencing the issue.
Here’s some demo code to reproduce what we’re seeing: http://cl.ly/1M1Y1L1J2y2u
And here’s a video of the demo code running: http://f.cl.ly/items/430m1b381x2W1j0Q3u1X/picker-bug-reproduced-2162.mov
Please file a bug report using the “Report a Bug” link at the top of the page. You will need to upload a .zip file that has running code that demonstrates the problem. It needs to have a build.settings and config.lua as well. Please also include your movies as extra files.
Thanks
Rob
Looks and sounds like this one :
24715 Framework - Widget Pickerwheel
soft landing fails to select correct target Important Open
@ksan: that bug you linked seems to be gone (or i don’t have permission to see it)
Can’t seem to find my case in fogbuz, but I’m curious if there has been any progress on this?
Haven’t seen anything in the daily changelogs.
Danny ,
I came across this discussion when I had one issue using
[lua]
widget.setTheme( “theme_ios” )
[/lua]
which gave me an error " widget.newPickerWheel: theme data file expected, got nil "
Is there any documentation to explain how to use theme file ?
Thanks
Abdul
You shouldn’t need to set the theme unless you want a specific theme. It will default to an iOS 7 like theme for iOS and an Android like theme for Android builds. That theme is for iOS 6 look and feel which Apple will start complaining about on Feb 1.
Rob
I see Rob,
in my case I got black buttons by default in the simulator… then I found the a tutorial to use this file but i was not lucky to make it work…
thanks
Abdul
You should use widget.setTheme( “widget_theme_ios” ) if you want the IOS 6 look. Details here :
ksan,
I did that but i want to use some custom colors for button using that external file but it didnt work even i saw it working in the tutorial …
it worked like css for the html …
regards
Abdul
I’m seeing issues with the pickerWheel not snapping to the closest value and not being able to scroll it to the last row of the column. Seems to happen with all pickerWheels using daily build 2014.2169 and above. Haven’t tried a build below that, if anyone has please confirm but 2169 is a bit far back as well.
Edit: tested all builds all the way back to .2155, still seeing the bug.
Edit2: .2141 as well, jumped all the way back to .2115. Still nothing. And when you scroll once and it doesn’t snap to the closest value, then you try scroll again and it throws a generic “Attempt to index field _values” error. I think it’s because I’m using the :getValues function on scroll stop and the second time you scroll it doesn’t know what value the scroll started from. Will probably also be squashed if the original bug is fixed.
Edit3: Seems to be a 1.0 compatibility issue as the widgetDemo works. Can you guys at CL please fix this asap as it would be great to be able to use the pickerWheel with the 1.0 compatibility mode, or just for the love of something implement an API that has the old G1.0 group properties and behaviors for positioning and what nots so us with old apps that have been under development for years with Corona and are heavily depended on the old group behaviors finally can migrate everything to the new engine. The group.anchorChildren API doesn’t work like 1.0 for nested groups and what have you.
Thanks
Using version 2014.2126 (2014.1.9). I’m having an issue where if you drag an item into the center and let go it doesn’t snap to the correct item. Any ideas on this?
Video:
I would suggest updating to 2159 or later (the last version with widget fixes) and if it’s still not working correctly, submit a sample project (make sure to include your build.settings and config.lua) along with your video. This landing issue should have been fixed a few widget updates back, but apparently something is still letting it get out of kilter.
Thanks
Rob
Hello Rob,
Thanks for the prompt response!
We went ahead and tried with 2014.2162, and are still experiencing the issue.
Here’s some demo code to reproduce what we’re seeing: http://cl.ly/1M1Y1L1J2y2u
And here’s a video of the demo code running: http://f.cl.ly/items/430m1b381x2W1j0Q3u1X/picker-bug-reproduced-2162.mov
Please file a bug report using the “Report a Bug” link at the top of the page. You will need to upload a .zip file that has running code that demonstrates the problem. It needs to have a build.settings and config.lua as well. Please also include your movies as extra files.
Thanks
Rob
Looks and sounds like this one :
24715 Framework - Widget Pickerwheel
soft landing fails to select correct target Important Open
@ksan: that bug you linked seems to be gone (or i don’t have permission to see it)
Can’t seem to find my case in fogbuz, but I’m curious if there has been any progress on this?
Haven’t seen anything in the daily changelogs.
I’m seeing issues with the pickerWheel not snapping to the closest value and not being able to scroll it to the last row of the column. Seems to happen with all pickerWheels using daily build 2014.2169 and above. Haven’t tried a build below that, if anyone has please confirm but 2169 is a bit far back as well.
Edit: tested all builds all the way back to .2155, still seeing the bug.
Edit2: .2141 as well, jumped all the way back to .2115. Still nothing. And when you scroll once and it doesn’t snap to the closest value, then you try scroll again and it throws a generic “Attempt to index field _values” error. I think it’s because I’m using the :getValues function on scroll stop and the second time you scroll it doesn’t know what value the scroll started from. Will probably also be squashed if the original bug is fixed.
Edit3: Seems to be a 1.0 compatibility issue as the widgetDemo works. Can you guys at CL please fix this asap as it would be great to be able to use the pickerWheel with the 1.0 compatibility mode, or just for the love of something implement an API that has the old G1.0 group properties and behaviors for positioning and what nots so us with old apps that have been under development for years with Corona and are heavily depended on the old group behaviors finally can migrate everything to the new engine. The group.anchorChildren API doesn’t work like 1.0 for nested groups and what have you.
Thanks
Yeah, I encoutered this exact issue. As a result of heavy dependence on the pickerwheel in my app, I migrated the whole thing to G2.
However, there are still other issues, such as the pickerwheel “jumping” a few entries, not properly snapping to entries, and displaying text in gray instead of black.
I’m using public build 2189.
I’m pretty sure this is another flavor of open issue 31640, which you can read about in this forum entry:
http://forums.coronalabs.com/topic/45794-tableview-positions-itself-wrong-in-10-compatibility-mode/
Yeah, it’s a 1.0 compatibility issue. tableView just doesn’t work in 1.0 compatibility.
Yeah, I encoutered this exact issue. As a result of heavy dependence on the pickerwheel in my app, I migrated the whole thing to G2.
However, there are still other issues, such as the pickerwheel “jumping” a few entries, not properly snapping to entries, and displaying text in gray instead of black.
I’m using public build 2189.