{ "id": "63356", "key": "TIMOB-2724", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "13271", "description": "Release 2.1.0", "name": "Release 2.1.0", "archived": false, "released": true, "releaseDate": "2012-06-29" }, { "id": "13406", "description": "Sprint 2012-10 API", "name": "Sprint 2012-10 API", "archived": true, "released": true, "releaseDate": "2012-05-20" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2012-05-11T16:31:56.000+0000", "created": "2011-04-15T03:27:50.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "SupportTeam", "api", "module_tableview", "qe-testadded" ], "versions": [ { "id": "11225", "name": "Release 1.5.0", "archived": true, "released": true, "releaseDate": "2010-12-14" } ], "issuelinks": [], "assignee": { "name": "vduggal", "key": "vduggal", "displayName": "Vishal Duggal", "active": false, "timeZone": "America/Los_Angeles" }, "updated": "2012-07-10T12:52:29.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
According to the API:
\r\n\r\nhttp://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI....
\r\nselectRow - programmatically select a row
I've tested this on the iphone and ipad and they both fail to\r\nselect a row. Attached below is a quick example.
\r\nedit:
\r\nIt seems this bug happens when there are rows that go off the\r\ndevice screen. If I do like 10 or 11 rows it works fine. 12+ it\r\nbreaks (on iphone)
On the iPad obviously you can fit more rows so this number will\r\nbe higher.
attached a new dumbed down version
Titanium 1.5.1 and iphone sdk 4.2
am I doing something wrong when posting bugs? Mine never seem to\nget assigned to anyone. Here is a thread of other people claiming\nits a bug
\n\nhttp://developer.appcelerator.com/question/96361/selectrow-on-a-tab...
Can we get some attention on this? TableView is a pretty common\nUI element that should be at least medium priority.
I found that selectRow works in 1.5.0 but not 1.5.1
ok I lied. I've come to this conclusion
\nIt seems this bug happens when there are rows that go off the\ndevice screen. If I do like 10 or 11 rows it works fine. 12+ it\nbreaks (on iphone)
\nOn the iPad obviously you can fit more rows so this number will\nbe higher.
I've noticed the same problem. I can reproduce the problem with\nonly 5 rows when the height of the rows are set to 100px. I agree\nwith Ronnie that when the rows go off the device screen the\nselectRow method will not work.
\nI have also noticed that selecting a single row causes another\nrow to automatically be selected. For instance, if I click the\nfirst row and select it, and then scroll down another row was\nautomatically selected.
\nIs there a workaround for this?
Why wasn't a bug like this fixed in the 1.6 release?? I screen\nrecorded a test app I made and you can see the list is\nlengthy...about 30 rows..If I start scrolling, random rows start to\nget selected. Note, I have no clicked on any rows..uhmmm??
\nDon I am selecting you as the \"who is responsible\". I've seen\nyou get many things fixed around here..well and I am just not\nfamiliar with anyone else.
Thanks for addressing this Don, but low priority? The list is\npretty unusable at this point. Also what does TBS stand for?
I've moved it over to the iOS lead to classify. It's not my\nposition to classify the priority of his items. TBS means \"To Be\nScheduled\"
I've found a solution to this which is described here:
\n\nhttp://developer.appcelerator.com/question/96361/selectrow-on-a-tab...
\nIn essence, TiUITableView delays setting the selection of the\ntable view until the last cell is display (for some reason).\nHowever, if the last cell is not visible then it won't trigger the\nselection.
\nMy work around is to remove the check for the last row, so it\nwill now trigger when the first cell is displayed. This works fine\nbecause it will only trigger once due to the initiallyDisplayed\nvariable being set to YES within the if statement.
\nIn TiUITableView.m change tableView:willDisplayCell:
\nif (initiallyDisplayed==NO && [indexPath\nsection]==[sections count]-1 && [indexPath row]==[section\nrowCount]-1)
\nto:
\nif (initiallyDisplayed==NO)