I have not tested the newest daily builds, but as of 2014.2135 isBounceEnabled does not work. It does nothing. Also, when applied to a scrollview horrible things happen. The scrollview jumps between where it’s trying to scroll and where it should’ve stayed.
Can anyone else reproduce this? I was able to using only a tableview with some rows and isBounceEnabled set to false.
There have been three daily builds since this and I’m seeing the issue in 2014.2146 still. Does anyone care to acknowledge?
There has been no fixes to widgets since 2109 so if you see an issue in 2135 it will still be there in 2146. There was another issue reported recently with isBounceEnabled so I guess it will get some attention sooner or later. In the meanwhile suggest not to move it and wait. Welcome to the " Waiting for Widget Fixes Club". :(
Oh I’ve been part of that club for a looooong time. :)
It just kills me that this worked in < 2135 and it’s broken now. It breaks an interface in our app that ships in two weeks. Very un-cool.
It does suck, but one good reason why daily builds are not usually suitable for releasing products on. That said, I have in the past after testing that the open issues didn’t affect my app. 
Yup. Its very uncool. Seems like something new is broken in there then. Suggest filing a bug report.
Someone else can file one if they want. I’ve filed at least 6 bug reports between this account and my other, and never so much as received a single response acknowledging them.
@thegdog you’re right that we shouldn’t and won’t ship an app using a daily build. Unfortunately the last public build has its own issues.
Yeah, hoping that we get to a new public release soon, just for the Tegra 2 fixes. If I move my app to the Graphics 2.0 engine, I want one that will be stable and work on all devices.
Thats my general experience as well and I agree its not exactly what I would call professional or ideal. IMHO, filing the bug gets you to put a stake in the ground and then remind CL publicly how neglected these things are…
See http://forums.coronalabs.com/topic/37217-list-of-open-widget-20-bugs-promised-features
Come join us on that thread. The more the merrier.
Oh I’ve been lurking in that thread for some time. I think I updated the google doc even (or at least intended to). It’s been great seeing you in so many threads saying exactly what myself and plenty others think.
I’ll hop back in that thread and raise any concerns I have there as well, thanks.
Super. Thank you very much.
My goal is to increase visibility as much as possible such that Corona Labs leaders can’t ignore these issues anymore. Widgets 2.0 release anniversary is fast approaching and key issues such as the one you have just encountered are still popping up on a regular basis. We need these issues to be eradicated and the only way thats going to happen is through a strong “Name & Shame” campaign. Sorry to see it had to come to this.
There have been three daily builds since this and I’m seeing the issue in 2014.2146 still. Does anyone care to acknowledge?
There has been no fixes to widgets since 2109 so if you see an issue in 2135 it will still be there in 2146. There was another issue reported recently with isBounceEnabled so I guess it will get some attention sooner or later. In the meanwhile suggest not to move it and wait. Welcome to the " Waiting for Widget Fixes Club". :(
Oh I’ve been part of that club for a looooong time. :)
It just kills me that this worked in < 2135 and it’s broken now. It breaks an interface in our app that ships in two weeks. Very un-cool.
It does suck, but one good reason why daily builds are not usually suitable for releasing products on. That said, I have in the past after testing that the open issues didn’t affect my app.
Yup. Its very uncool. Seems like something new is broken in there then. Suggest filing a bug report.
Someone else can file one if they want. I’ve filed at least 6 bug reports between this account and my other, and never so much as received a single response acknowledging them.
@thegdog you’re right that we shouldn’t and won’t ship an app using a daily build. Unfortunately the last public build has its own issues.
Yeah, hoping that we get to a new public release soon, just for the Tegra 2 fixes. If I move my app to the Graphics 2.0 engine, I want one that will be stable and work on all devices.
Thats my general experience as well and I agree its not exactly what I would call professional or ideal. IMHO, filing the bug gets you to put a stake in the ground and then remind CL publicly how neglected these things are…
See http://forums.coronalabs.com/topic/37217-list-of-open-widget-20-bugs-promised-features
Come join us on that thread. The more the merrier.
Oh I’ve been lurking in that thread for some time. I think I updated the google doc even (or at least intended to). It’s been great seeing you in so many threads saying exactly what myself and plenty others think.
I’ll hop back in that thread and raise any concerns I have there as well, thanks.