{ "id": "63635", "key": "TIMOB-3003", "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": [], "resolution": { "id": "3", "description": "The problem is a duplicate of an existing issue.", "name": "Duplicate" }, "resolutiondate": "2013-11-10T07:12:18.000+0000", "created": "2011-04-15T03:34:28.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "core" ], "versions": [ { "id": "11233", "name": "Release 1.6.0", "archived": true, "released": true, "releaseDate": "2011-02-23" }, { "id": "13505", "description": "Release 3.0.0", "name": "Release 3.0.0", "archived": true, "released": true, "releaseDate": "2012-12-14" } ], "issuelinks": [ { "id": "33137", "type": { "id": "10002", "name": "Duplicate", "inward": "is duplicated by", "outward": "duplicates" }, "outwardIssue": { "id": "92848", "key": "TIMOB-9400", "fields": { "summary": "iOS: Children are not removed from parents view hierarchy when context is shutdown", "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" } }, "priority": { "name": "High", "id": "2" }, "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } } ], "assignee": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-09T21:30:32.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}
if I open a window with inside a tableview with\r\ntransparent background, will be fine the first time I open\r\nthat window, but then if I open it again I will see an empty\r\ntableview in the background.
\r\nProject type iPad
\r\niOS SDK 4.2
\r\nTitanium SDK 1.6.0
\r\nTitanium Developer 1.2.2
I really need help with this, my app keep creating overlapping\ntableviews for no reasons
Hi alberto, can you publish your code?
I've attached an example project, I thought it would've been the\neasiest way since my code is on 3 different files.
\nJust try to click on the button on the first page and then on\nthe log out button from the second page. If you repeat this back\nand forth you'll see something weird, another empty tableview in\nthe background (as in the screenshot from my original ticket).
\nI even tried the last 1.6.0 continuous, but didn't make any\ndifference.
Hi,
\nYour problem is because when you click the close button of the\npage2.js \"win.close ();\" will destroy the objects.
\nWhen you open again in the button on the page1.js\n\"Titanium.UI.currentTab.open(WIN2 {animated: true});\" is opening a\nscreen residual properties and without this there is no bottom\nviewer.
to correct, change your page1.js to:
\n\n\nvar win = Ti.UI.currentWindow;\n\nvar button = Ti.UI.createButton({width:100, height:50, title:'button'});\nwin.add(button);\n\nbutton.addEventListener(\"click\", function(){\n\n var win2 = Titanium.UI.createWindow({ \n url:'page2.js',\n title:'Tab 2',\n backgroundColor:'#fff',\n backgroundImage:'bgIndex.png'\n });\n\n Titanium.UI.currentTab.open(win2,{animated:true});\n});
\n
\nTo create a new window before open.
I still think it's a bug, since I'll waste resources in\nrecreating the window every time I click the button.
\nThank you anyway for your quick reply, at least I know how to\nfix it for now.
Should maybe invalidate because there's a workaround and memory\nteardown is required?