No news ?
A good number of the issues on the list are dating back to June / July 2013. We have heard “next week” mentioned a couple times now along those painful months of waiting. Is Corona Labs release management process so unorganized that we can’t be given a solid ETA to count on?
I’d like to think that Corona Labs management knows what’s on the hot plate, how long it will take to deliver and then how to go about delivering it… The only conclusion I can draw to us not getting these fixes despite having to wait for months and months for them is that perhaps Corona Labs management does not feel they are crucial to the success of Corona Labs and its product. Oh wait, we don’t even need to speculate… This was openly stated not long ago by David Rangel (%1 of Corona SDK comment…).
Please just give us a firm ETA, what will be fixed by then and then do it. This waiting game is really not professional at all. Thank you very much.
For anyone specifically still waiting for reRender, there is an alternate techniqueue to change row items and have them update instantly, as I pointed out above. I’ve used it to update images in rows, and to update text as well (posted 6 minutes ago --> 7 minutes ago). I’ve also managed to find a workaround for every other table view problem I had when migrating to 2.0… For sure things changed a lot in the last week, but right now, my table views are formatting and updating like a top… So IMHO the table view 2.0 seems to be pretty good ATM. (There were a variety of positioning changes coronaLabs made in the last week that screwed up my table view layout, but easy to adapt to). In my case, I’d just as soon have them leave it alone, so my workarounds aren’t invalidated 
On the other hand, not everything is great in mpappas land… when my app suspends / resumes, it loses focus or something, and input doesn’t work properly, but haven’t got to look into that issue and whether it has anything to do with the table view.
Just noticed 1260! Will try tonight once back home. Sounds exciting.
Hi Kerem (and others),
I’ve said it before, but I’ll say again that I appreciate your patience on this. Sincerely. We are keenly aware of these bugs, and we don’t consider them a “1% of users” type of feature, not even close. I don’t recall David making that statement, and if it was made, it may have been taken out of context, and it was not intended in that manner.
As you just noticed, build #1260 introduces several widget fixes. I realize it does not fix ALL of your reported bugs, but we are continuing to work on these (every day, in fact).
I can’t provide a specific ETA, nor will I continue saying “next week”… just that we are aware of most/all widget issues, and we are squashing them one by one as time and engineering resources allow.
Brent
Hi Brent,
Thanks for your kind response. I am appreciative of the work that goes into these fixes despite all resource constraints. I will run through the update and provide specific feedback as needed. Seems like some new problems might be creeping up. I just hope we don’t have to wait for another 4-5 months for the issues to be addressed on a batch basis.
Regards & thanks,
Kerem
+1 could use it right now actually (just hit a situation where I need it)
any news on re-render?
Well, Alex mentioned in another thread that the long awaited batch of widget fixes would be forthcoming this week so fingers crossed we might have a fix for this one.
Any news on this ? Where exactly on the list is it ? Is it a big list ?
Dont know about anybody else but I am loosing the will to live
We are working on getting these fixes in as quickly as we can. These are important for us to fix. We are not ignoring them.
I don’t have a list of what’s being fixed.
Rob
A good number of the issues on the list are dating back to June / July 2013. We have heard “next week” mentioned a couple times now along those painful months of waiting. Is Corona Labs release management process so unorganized that we can’t be given a solid ETA to count on?
I’d like to think that Corona Labs management knows what’s on the hot plate, how long it will take to deliver and then how to go about delivering it… The only conclusion I can draw to us not getting these fixes despite having to wait for months and months for them is that perhaps Corona Labs management does not feel they are crucial to the success of Corona Labs and its product. Oh wait, we don’t even need to speculate… This was openly stated not long ago by David Rangel (%1 of Corona SDK comment…).
Please just give us a firm ETA, what will be fixed by then and then do it. This waiting game is really not professional at all. Thank you very much.
For anyone specifically still waiting for reRender, there is an alternate techniqueue to change row items and have them update instantly, as I pointed out above. I’ve used it to update images in rows, and to update text as well (posted 6 minutes ago --> 7 minutes ago). I’ve also managed to find a workaround for every other table view problem I had when migrating to 2.0… For sure things changed a lot in the last week, but right now, my table views are formatting and updating like a top… So IMHO the table view 2.0 seems to be pretty good ATM. (There were a variety of positioning changes coronaLabs made in the last week that screwed up my table view layout, but easy to adapt to). In my case, I’d just as soon have them leave it alone, so my workarounds aren’t invalidated On the other hand, not everything is great in mpappas land… when my app suspends / resumes, it loses focus or something, and input doesn’t work properly, but haven’t got to look into that issue and whether it has anything to do with the table view.
Just noticed 1260! Will try tonight once back home. Sounds exciting.
Hi Kerem (and others),
I’ve said it before, but I’ll say again that I appreciate your patience on this. Sincerely. We are keenly aware of these bugs, and we don’t consider them a “1% of users” type of feature, not even close. I don’t recall David making that statement, and if it was made, it may have been taken out of context, and it was not intended in that manner.
As you just noticed, build #1260 introduces several widget fixes. I realize it does not fix ALL of your reported bugs, but we are continuing to work on these (every day, in fact).
I can’t provide a specific ETA, nor will I continue saying “next week”… just that we are aware of most/all widget issues, and we are squashing them one by one as time and engineering resources allow.
Brent
Hi Brent,
Thanks for your kind response. I am appreciative of the work that goes into these fixes despite all resource constraints. I will run through the update and provide specific feedback as needed. Seems like some new problems might be creeping up. I just hope we don’t have to wait for another 4-5 months for the issues to be addressed on a batch basis.
Regards & thanks,
Kerem
I’ve tried 1260 to fix my tableview issues. Things looks better but I now have a storyboard problem - enterScene is not firing in one of my scenes. It just seems to happen with one scene deep down in my app - so I am a bit lost to even reproduce it for a bug submit. So I’ve had to roll back to 1202.
Anyways, has anyone outside of corona tried to build the widget framework at https://github.com/coronalabs/framework-widget ?
I tried to build the code to try to incorporate into my 1202 SDK - I could certainly use some help from folks who have done it before.
Cheers!
Praveen
Hi Praveen, I am using a custom build of the widgets library and have checked in some changes in a fork on github as well. Let me know what kind of help you need Atanas
The code on GitHub now seems to be post G2 conversion and has code catering for G1 compatibility etc. This means you should really try and use it with 2013.2076 onwards builds. You can try the latest daily build, 2013.2100 with G1 compatibility and see if your app runs without much need for G2 conversion. Good luck.