@ksan: look at 2013.2109.
alex
Wow! How did you manage to fit all that through the chimney? :) Thank you very much for the hard work! The list looks extensive and great!!! I am sure we will all be busy testing for a while. Hope you enjoy a well deserved break. Happy Holidays!
Hi Alex, Great to see this update Can you please push the latest widgets sources to github Thanks Atanas
Unfortunately still there, but I much appreciate that widgets are more observed now by corona. Keep going 
Thanks and happy holidays to all corona users and staff!
@sunmills: i did not forget about it. It will be taken care of in the next iteration (which will be soon).
alex
Alex , thank you very much for your hard work. This was certainly a nice bundle with lots of fixes and improvements. It is much appreciated.
All subscribers of this thread… I hope this message finds you well. I was going through the widget bugs spreadsheet to move the items that are fixed to the new Fixed tab and noticed there are a number of items which might have been fixed. I moved the ones that I can confirm but there are a number of them which I can’t easily confirm as fixed.
When and if you have a moment could you kindly take a look and see which ones you can confirm as fixed? Please simply put a remark such as Fixed on the Remarks or Notes column and I will do the cleaning up (ie moving them to the other tab).
Just want to recognize CL staff for the good work done in this area by clearing the spreadsheet as much as possible. This will also allow them to re-focus on the remaining items. There is some good momentum of late and I hope to keep it going by making sure what still needs to be tackled is visible clearly.
Thank you very much for your time and attention. Wishing you all a wonderful holiday season.
Regards,
Kerem
Thanks Ksan, your benevolent work and kind attitude are an inspiration for the rest of us to try help out the community and make Corona a better tool for business apps. Happy holidays Atanas
He didn’t mean it in the sense of go and fix it yourself. But Corona doesn’t offer jour bugfixing and if the bug is holding you back and you can’t afford to wait, Ford would advice you to change your own tires as well.
Edit: Forgot to add the reason I came to this thread… I’m having the same issue as people earlier in this thread. If I’ve got a list of multiple rows and I delete the first row in the tableView, it will animate the remaining rows weirdly, pushing the next coming row up perfectly but not the ones following it.
Also is there a way to disable the animation altogether?
Thats exactly what he meant. And its not a case of changing the tyres.
And I said nothing about changing tyres !
Fine. Ford would tell you to go to a private mechanic to fix your steering wheel if you couldn’t wait.
Ever heard of the Ford SUV tire recall? Trust me, in these litigious times no company can afford to sell something broken and then tell you to go fix it yourself. Thankfully nothing we do with the widgets lead to such fatal outcomes but still, what is broken needs to be fixed.
I am thankful to Corona Labs for continued efforts to improve this situation but also can’t help but get frustrated in how long it has taken. IMHO, visibility leads to awareness and focus. So best you can do is to add your bugs to the spreadsheet and edit your lines occasionally when your bugs have been fixed. Lets keep the spreadsheet up to date and hope that it continues to catch attention at Corona Labs.
Thanks for all the contributions to this thread and the spreadsheet. All the best.
Wohoo! Big list of fixes in 2013.2096. Thanks guys!!! Giving this a go now.
EDIT - Confirmed fixes :
- tableView:scrollToIndex() is good once again.
Very nice.
Everything fixed for me except delete row behavior (case 28476, code example: http://pastebin.com/93Eh1Vrs).
I also have one bug that I have not submitted yet because my simplified test case works. Where tableView:scrollToY does not work in willEnterScene in my project, worked prior to G2. Need to figure out what is going on there.
The background color bleed through issue seems to be there as well but thats a minor one against all others. Delete issues are big.
Where is it bleeding? It used to bleed through between rows for me before this release, OK now.
As mentioned in this thread : http://forums.coronalabs.com/topic/41623-2-possible-problems-with-tableview-in-g2/#entry217593
Seems like the issue is still there but so be it.
@ksan: That’s not a bug, but rather a missing feature. In iOS7 the tableView separators are indented by default, we lack the implementation of a setIndent so you can actually create a separator for the complete tableView contentWidth. Will be done.
@jonjonsson: Looking at 28476 now. Thanks again for the great bug reports.
Alex.
Just out of curiosity, why would they have the separators indent by default? It doesn’t make sense and just looks buggy?
@Skatan: It does make sense visually. It gives a nice touch to the left side being cleaner, shifting focus on the table row information. Look no further than the contacts view to see what i mean. Nevertheless, as mentioned in my previous post, they do allow you to set the indent of the separator to 0 so it restores iOS <7 behavior, and we’ll expose that as well very soon.
alex