Hi Richard, I would never delete entries from a list like this. As I mentioned in my post right above yours I was contemplating hiding the rows for resolved / fixed bugs but I can see this will cause confusion. I think your idea is a better one to gray them out and move them to the end of the list etc. I will do that from now on. Thanks much for your suggestion.
Ah I didn’t look at the doc history. Just saw a solved bug was deleted from the sheet.
Hi Alexf, any update on this issue? It is quite urgent as we are waiting this to release our game.
Still more fingernail biting as the list continues to grow. Any ideas on when the next widget updates might occur? Thanks much for keeping it going.
Hi Kerem,
Alex is exceedingly busy these past couple weeks with some very high-priority tasks, so I can’t tell you exactly when the next batch will roll in.
I also inspected your “transition bug”. Why are you calling the list population on an onComplete? I tried simply calling “loadSQLList” directly, then transitioning, and everything works fine. I don’t mean to sound dismissive, but I’m not quite seeing the practical use case of populating a list based on a transition timer. Please explain the intention here.
Thanks,
Brent
Hi Brent, thanks for letting us know about Alex.
I wasn’t worried about the transition.to bug really. There are many more higher impact bugs in the list than that one. I don’t have a use case for the transition.to situation. It actually came out as I was helping a fellow Corona SDK beginner like me. See the following thread : http://forums.coronalabs.com/topic/37825-tableview-using-sqlite-database/#entry196896. I reported that one because it is an anomaly. Any part of Corona API should not cause a malfunction in any other part. Or at least if its meant to be that way it should be documented in the Gotchas.
Moving on, I’m much more worried about and keen to see improvements in tableView deletion issues as well as #24995 etc. Guess all that will have to wait for Alex to resurface. Thanks for the update anyways.
I’ve just posted up a bug as well. It isn’t major, if you consider it means I can’t use segmented controls at all in my program and have to write my own version, but there you go. It is likely the red-headed step-child of the controls anyway, but realistically I wish I’d never started trying to customise (visually) the widgets, it has only brought me a world of pain…
http://forums.coronalabs.com/topic/38211-attempts-to-customise-segmented-control-unusable/
@rakoonic - Thank you very much for your contribution to this list. I am very concerned about the visual customizations as well. IOS 7 is around the corner and everyone and their cats are busy giving their apps the “flat” make over. I was hoping by now Corona Labs would have released an update to the widgets containing an IOS 7 look alike theme but I guess there are bigger priorities at play. We are each to fend for ourselves I think.
Indeed - so much so I wrote my own segmented code from scratch - it should work as a complete replacement, and only needs one extra parameter over the stock widgets one - you need to pass the theme file.
http://forums.coronalabs.com/topic/38218-new-segmentedcontrol-replacement-code-here/
Frankly at this point I am genuinely considered writing my own replacement widget code for the ones I use (granted I don’t use all of 'em, and I haven’t encountered problems with all of the widgets, but there seems to be no effort being placed into fixing bugs. Having said that, given what I saw in github for the segmented control, it doesn’t really need a bug fix so much as a complete re-write.
However, my re-write only took a few hours although I am the first to admit it needs more error handling etc, but with all things considered, I think you should be able to churn out a couple of the simpler widgets completely re-done per day. Now if only someone would pay me to do so 
Hi Kerem,
We will provide a basic iOS7 theme when it’s realistic, but Apple’s NDA is still preventing this (and no doubt some of the look and feel is still undergoing changes internally within Apple). So we can’t officially release anything to you at this point. As for the other issues, we should be returning to resolving some of these this week, and I will be preparing the next theming tutorial as soon as these are cleared.
Brent
Yeah I figured the NDA would be in the way. 
rakoonic: I want to look at your segmented widget code later (quite frankly I forgot it was even readded to the widgets for some reason) simply because I seem to do the same thing now and then (writing my own hasty widgets) but I will tell you right now that segmented control is about 50x simpler to write than, say, tableView or scrollView…I’m not sure if I’m scared or excited by the idea of looking at the code for those on github…
Alex was working hard to crush bugs (I would know, he’s closed what, 4-5 of mine in the last two months?) so the effort is definitely there. It just gets taken up by higher priority engine issues sometimes, as far as I can tell.
Hi Brent, I hear you loud & clear.
The rumour on the street is now September 10 for the new iPhone release which means IOS 7 will also be out of NDA at that point. This is now less than a month from now. Scary deal! It would be great if CL could target the same date for the release of updated widgets / templates then… Meanwhile, we are all under the same Apple NDA so perhaps an early release for testing purposes could occur to a select group of ‘avid’ widget users. I would be more than happy to oblige by my Apple NDA and a Corona Labs add-on NDA (if required) if I was to somehow end up with a copy of the future IOS7 theme for the widgets …
Great news on return of focus to widgets. Alex is great at resolving these issues but I guess he is limited by the number of hours in the day and what his boss tells him to work on! 
We appreciate all the hard work from Alex, yourself and everyone else in the team. That follow-on to your tutorial will be most appreciated too. Thank you very much.
Regards,
Kerem
Yeah obviously segmented controls aren’t the most difficult at all, but I’ve done my own scrollviews anyway, and am about to tackle my own list views (both due to needing features not in nor likely to ever come, and bugs - have you seen how bad the scrollbar is on scroll views? Why, I have no idea, it really isn’t tough). None of them are actually that tricky (list view is likely the worst), although I’m still steering clear of masks for as long as possible, hoping that containers arrive before I need them
If Alex gets back onto things, then great, but I can’t imagine anything I’ve uncovered will be high priority compared to many items on his list, even though for me they’ve proved to be enough to force me to do it all from scratch
Anyone else experiencing a bug with tableview categories?
When scrolling a tableview up the top category changes to match the contents of the last row in the tableview. With so many changes to widgets I am not sure at this point if it’s a bug or me.
It seems to work well for me. I’m not observing the bug you mention. Suggest you try changing WidgetDemo in your side and see if you can duplicate the issue.
How are the other fixes coming along?
Please add to the spreadsheet if you observe and report any other bugs.
Have a great weekend.
Updated with - Case 25367 - transition.to causes tableView Category sticky at the top behavior to malfunction
Hi, I am currently using 2013.1179, and the .deleteRow() is not working.
This is the log:
?:0: attempt to index field ‘_scrollBar’ (a nil value)
stack traceback:
[C]: ?
?: in function <?:989>
Even the code in documentation is NOT working. (not the ‘missing list’ error, I replaced with ‘tableView’).
I remember it was working 1 month ago.
Hi topfuncoolgames,
Confirming that. Please use the event release phase of the listener to delete rows, i’ll post a fix today for that specific case.
Thanks,
Alex
Thanks Alexf! I will wait for that.