TableView delete row problems

Getting Started Newbie Questions
#1

Starter v2014.2189 on OS X v 10.9.2
Anyone having problems with deleting tableview rows?

  1. Let’s say I have 5 rows. If I delete row 4, and click on the last row, the index value is still 5 instead of 4.
    Is this intended behavior?

  2. After deleting a middle row, they rows seem to visually overlap and sometimes I don’t even see the horizontal line separating the rows.

I was previously using a really old version of Corona and afaik this did not happen in that version.

Thanks,
BVS

#2

Do you know which daily build has it been fixed?

#3

I believe the last batch of widget fixes went out in 2282.

Rob

#4

Hi Rob,

Thanks for the reply. I just downloaded 2282 and tested it. The problem is not fixed. This is a bug in the Table View widget. 

Tian Choh

#5

Thanks bvsmailuser, I have been noticing this as well.

#6

Engineering will likely reject the bug report without a working sample app that includes both a config.lua and build.settings.  If you did not provide those please update the bug.  You should be able to reply and attach it as a file.

Rob

#7

Hi Rob,

I have submitted the code and all required information 2 days ago. However, I have yet to get a reply from your Engineering group. In the code, I have printed out the index of the tableView and it clearly showed that the row index was not updated after the delete row. This mess up the data if you use the row index for reference.

BTW, when do you think engineering can get back to me or at least send me an acknowledgement that you have received my bug case reporting.

Thanks.

Tianchoh

#8

Yes. This was fixed. The problem that I am highlighting is that the row index tableView does not get updated and so, if you do another delete below the row of the previous delete, you will not get the correct current row index. This is no good because, if you use the index to read data, you end up getting the wrong data.

Can you enlighten me a bit more on how the work around that you proposed works? do you have some sample code for reference?

Thanks.

Tianchoh

#9

Hi BVS,

The table database consists of existing past data which is loaded from a database file. The user can also input and edit the information. Thanks and looking forward for your code snippet.

Thanks.

Tianchoh

#10

BVS, I was just getting ready to suggest using the passable parameters as a way to decouple the tableView’s row index from the data in another table.  Usually the problem comes from category rows which count as rows with regards to the row index but almost never match up with data rows in a data table.  

As for the display issue, that seems kinda odd.  Please post your bug numbers here so I can find them and see what’s going on.  For starter’s who are still using 2189, be aware that we fixed a bunch of things in 2282.  You won’t see these until the next public build as daily builds are for Pro and Enterprise subscribers only.

Rob

#11

Do you know which daily build has it been fixed?

#12

I believe the last batch of widget fixes went out in 2282.

Rob

#13

Hi Rob,

Thanks for the reply. I just downloaded 2282 and tested it. The problem is not fixed. This is a bug in the Table View widget. 

Tian Choh

#14

Thanks bvsmailuser, I have been noticing this as well.

#15

Engineering will likely reject the bug report without a working sample app that includes both a config.lua and build.settings.  If you did not provide those please update the bug.  You should be able to reply and attach it as a file.

Rob

#16

Hi Rob,

I have submitted the code and all required information 2 days ago. However, I have yet to get a reply from your Engineering group. In the code, I have printed out the index of the tableView and it clearly showed that the row index was not updated after the delete row. This mess up the data if you use the row index for reference.

BTW, when do you think engineering can get back to me or at least send me an acknowledgement that you have received my bug case reporting.

Thanks.

Tianchoh

#17

Yes. This was fixed. The problem that I am highlighting is that the row index tableView does not get updated and so, if you do another delete below the row of the previous delete, you will not get the correct current row index. This is no good because, if you use the index to read data, you end up getting the wrong data.

Can you enlighten me a bit more on how the work around that you proposed works? do you have some sample code for reference?

Thanks.

Tianchoh

#18

Hi BVS,

The table database consists of existing past data which is loaded from a database file. The user can also input and edit the information. Thanks and looking forward for your code snippet.

Thanks.

Tianchoh

#19

BVS, I was just getting ready to suggest using the passable parameters as a way to decouple the tableView’s row index from the data in another table.  Usually the problem comes from category rows which count as rows with regards to the row index but almost never match up with data rows in a data table.  

As for the display issue, that seems kinda odd.  Please post your bug numbers here so I can find them and see what’s going on.  For starter’s who are still using 2189, be aware that we fixed a bunch of things in 2282.  You won’t see these until the next public build as daily builds are for Pro and Enterprise subscribers only.

Rob