{ "id": "61270", "key": "TIMOB-638", "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": "11225", "name": "Release 1.5.0", "archived": true, "released": true, "releaseDate": "2010-12-14" } ], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-15T02:33:26.000+0000", "created": "2011-04-15T02:33:24.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "1.0", "ios", "iphone", "mobile", "scrollview", "tableview" ], "versions": [], "issuelinks": [], "assignee": { "name": "rseagraves", "key": "rseagraves", "displayName": "Reggie Seagraves", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-02T18:50:00.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}
When constructing a scrollView containing one Tableview followed\nby 2 ordinary views all was well.
\nWhen a fourth view was added, scrolling to the third and back is\nOK, but scrolling to the fourth and back to the first: the\ntableview has been dropped.
\nexample app.js attached to aid reproduction and diagnosis.
\ncheers,
\nChris.
P.S
\nMac OSX 10.6.2 iPhone SDK 3.1.3, Ti Mobile 1.0.0
Could this be memory manager 'release'ing views prematurely?\nWith only four views, moving between them I end up with only one of\nfour showing and the other three lost.
Had a check in the source code - heres the problem:
\n\n// the goal of this logic is to simply attempt to keep 3 frames\n// in memory at a time (attached to the view tree)\n// depending on the direction it will keep the \n// current frame +1 and -1 available so that those are immediately\n// visible when you scroll
\n
\nThis is a BUG - there's no limit on how many tabs are allowed by\nthe developer.
\nAnd nothing in any documentation to suggest such a limit.
Please fix.
I'm unable to reproduce the issue using TiMobile 1.4.1, iphone\n4.0 sdk (mac os10.6.4)