[TIMOB-3003] iOS: Problems with Grouped TableView
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2013-11-10T07:12:18.000+0000 |
Affected Version/s | Release 1.6.0, Release 3.0.0 |
Fix Version/s | n/a |
Components | iOS |
Labels | core |
Reporter | albertomarcone |
Assignee | Ingo Muschenetz |
Created | 2011-04-15T03:34:28.000+0000 |
Updated | 2017-03-09T21:30:32.000+0000 |
Description
if I open a window with inside a tableview with transparent background, will be fine the first time I open that window, but then if I open it again I will see an empty tableview in the background.
Project type iPad
iOS SDK 4.2
Titanium SDK 1.6.0
Titanium Developer 1.2.2
Attachments
File | Date | Size |
---|---|---|
resources.zip | 2011-04-15T03:34:28.000+0000 | 276937 |
tableviewbug.png | 2011-04-15T03:34:28.000+0000 | 47574 |
I really need help with this, my app keep creating overlapping tableviews for no reasons
Hi alberto, can you publish your code?
I've attached an example project, I thought it would've been the easiest way since my code is on 3 different files.
Just try to click on the button on the first page and then on the log out button from the second page. If you repeat this back and forth you'll see something weird, another empty tableview in the background (as in the screenshot from my original ticket).
I even tried the last 1.6.0 continuous, but didn't make any difference.
Hi,
Your problem is because when you click the close button of the page2.js "win.close ();" will destroy the objects.
When you open again in the button on the page1.js "Titanium.UI.currentTab.open(WIN2 {animated: true});" is opening a screen residual properties and without this there is no bottom viewer.
to correct, change your page1.js to:
To create a new window before open.
I still think it's a bug, since I'll waste resources in recreating the window every time I click the button.
Thank you anyway for your quick reply, at least I know how to fix it for now.
Should maybe invalidate because there's a workaround and memory teardown is required?
Confirmed SDK 2.2.0.014b86f. Color must have an incorrect lifecycle.
Closing ticket as duplicate.