[AC-2358] TableView delete row indexing issues
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | n/a |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2013-10-14T17:14:24.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Titanium SDK & CLI |
Labels | TableView, tableViewRow |
Reporter | Far |
Assignee | Mostafizur Rahman |
Created | 2013-10-09T23:42:21.000+0000 |
Updated | 2016-03-08T07:41:23.000+0000 |
Hello Far, Can you please describe this issue more clearly with full test code and test case? That is can test with app.js file. Thanks
SDK 3.1.3 iOS 7 XCode 5
1. Delete any row from 0 to 3 from table by standard iOS table action 2. Click row that was *after* deleted 3. You will get *** Assertion failure in -[UITableView _endCellAnimationsWithContext:], /SourceCache/UIKit_Sim/UIKit-2903.2/UITableView.m:1076 Look like invalid row returned in event. Row index is valid but no chance to get valid row by any TableView function. table.setData(table.getData()) in 'delete' event resolve this issue but it's ugly hack.
Hello, tested with iOS7, Ti 3.1.3. When you delete the rows, there is no warning nor failure. Best, Mauro
row.hasCheck = !row.hasCheck; not work for any row *after* deleted. You will get assertion if click last row after delete any except last.
Look like the problem in
function. After delete row from section
there is need to fix row index (TiUITableViewRowProxy *row* property) in all rows after deleted.
Hello, I used your testcase, instructions and it's not failing. If you can provide a testcase that reproduces the issue, we can reopen this. Best, Mauro
Application don't crash but has wrong behavior after delete row. 1. Click last row several time. You will see that *hasCheck* property set properly. 2. Delete first row. 3. Click last row. *hasChecked* property will not change and you will get *** Assertion failure in -[UITableView _endCellAnimationsWithContext:], /SourceCache/UIKit_Sim/UIKit-2903.2/UITableView.m:1076 in console.
Hello Far, your several times is 'dozens of times per second'? Best, Mauro
It's not necessary. I made the video for this issue https://mega.co.nz/#!Z89zVZLJ!YSjfqgLZHa96oEKycAnG9xoS9mcL4R7cbZa9xyTMJKU
Watch this video (it's very short - only 14s) and reopen ticket please, so I can forget about this issue before next release, when I say: "Good work, guys!".
Look like fixed in master. Thx.