wrong positioning of rows in table view when one is deleted

I think there is the way to make it right through the scrollview.

Please let me know if it works for you, thanks!

Patso, I wrote a sample app and filed a bug: Case 32773 for build v2014.2189. Seems to occur with delete when you have more than one object per row, not sure. Have you device tested this? Thanks, BVS

I’ve tested both on IOS and android. same problem. I’ll try to make it with one object per row.
thanks for bug report:)

Patso, I just received email that this problem has been fixed in the daily build. They are fast!

I don’t have access to it, so I can’t test right now.

Thank you Corona support for being very responsive!

so how can I access the changes if I’m a starter. They will be included in the new release?

I was told they don’t have a release date yet for the next public build. I’m in the same boat - I can’t afford pro license right now to have access to daily build :frowning:

so screw it I’m doing the stuff in scrollview

Ok, please tell me if it works for you.

I have access to the daily build but it does not seem to be fix yet. Do you know which build fixed the problem?

Tianchoh, perhaps you could ask a staff to test it for you. I had submitted a bug report along with a small sample app, case 32773. I was told in the response that this was already fixed in a daily build but I didn’t have access to it myself. I was also waiting for a fix with radio buttons to become public, so I’ve given up on using Corona for now because I didn’t have time to wait. Good luck, BVS.

Thanks BVS. I have also raise a bug case to Corona and will see what they say. In the meantime, I will have to find a work around for it. I am thinking of using sqlite3 for database and then get the module to reload the database to fill up the table again each time a delete occur.

That might work. Delete the tableview and reload the new table. The sqlite sql operations all work as expected - create, insert, update, delete. Good luck,