[TIMOB-1530] Android: deleting nonexistent row generates runtime error
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:56:25.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 |
| Components | Android |
| Labels | android, defect, regression |
| Reporter | Thomas Huelbert |
| Assignee | Don Thorp |
| Created | 2011-04-15T02:55:16.000+0000 |
| Updated | 2011-04-17T01:56:25.000+0000 |
Description
found on 1.4.1 f88b9e
1.kitchenSink>baseUI>Views>Table Views> Delete
Row
2.delete until there are no more rows, delete again
results: runtime error
(from [78ca20f1fc77df35bda995a076e89daf446a39da]) [#1530 state:fixed-in-qa] This is actually doing the right thing in Android. Blain and I walked through it and he agreed that iPhone should be throwing an exception. I added an exception handler to the test so that it deals with the expected exception. The delete from top is also correct. The test is actually very broken because tableview.data is actually an array of TableViewSections's not rows. It's a hold over from pre 0.9. The length of that array is 1 therefore it always remove index 0. http://github.com/appcelerator/titanium_mobile/commit/78ca20f1fc77df35bda995a076e89daf446a39da"> http://github.com/appcelerator/titanium_mobile/commit/78ca20f1fc77d...
confirmed, loggin new crash bug for using touch on the button.