{ "id": "62603", "key": "TIMOB-1971", "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": "11229", "name": "Release 1.5.0 M04", "archived": true, "released": true, "releaseDate": "2010-12-06" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:57:41.000+0000", "created": "2011-04-15T03:06:55.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "android", "defect", "performance" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:57:41.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": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}

We got a clarification today that TableViewRows that have the\nsame structure are not allowed to change their layout. Previously\nwe interpreted that they had to have the same controls in the same\norder, but layout might not be identical.

\n

Optimize Rows such layout only occurs when a new internal row is\ncreated and when reused, only the data from each control is\napplied, not layout.

{html}", "attachment": [], "flagged": false, "summary": "Android: Optimize TableViewRow Layout with Same Classname", "creator": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "127125", "author": { "name": "mculpepper", "key": "mculpepper", "displayName": "Marshall Culpepper", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

(from [e18980e31ba5c0e061da3ababd711467471bffeb])\npre-seed a relatively large number of row types so we can avoid\ncalling setAdapter to tell the ListView about new row types (which\ncauses all kinds of memory / model havoc). added a new\nforceCreateView in TiViewProxy to simply assign the internal view\nreference to a new instance, rather than forcefully tearing down\nthe existing view. this fixes the className redrawing bug when the\nListView recycler shuffles reused view instances [#1971\nstate:fixed-in-qa] [#2377 state:fixed-in-qa] [#2344]\n\nhttps://github.com/appcelerator/titanium_mobile/commit/e18980e31ba5...

{html}", "updateAuthor": { "name": "mculpepper", "key": "mculpepper", "displayName": "Marshall Culpepper", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T03:06:56.000+0000", "updated": "2011-04-15T03:06:56.000+0000" }, { "id": "127126", "author": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

used KS example for linked bug to close this.[INFO] Titanium SDK\nversion: 1.5.0 (12/08/10 08:34 4ee1205) G2 + 2.1 sim

{html}", "updateAuthor": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T03:06:56.000+0000", "updated": "2011-04-15T03:06:56.000+0000" } ], "maxResults": 2, "total": 2, "startAt": 0 } } }