My app is a type of calculator. Once the user clicks the button\nCalculate, a new window is opened that shows the results. On this\noutput window I have added a back button which closes the current\nwindow. This all works fine unless upon clicking back you once\nagain click calculate. This time, the window opens but the\nbackground is black and none of the buttons work, even hitting the\nAndroid back key.
\nWhat is happening? Was the output window never fully closed?
I've run into this same problem. It happening to me in Android\n1.5.1+. Probably in 1.5.0 as well, but I haven't tested it. It\nappears to me like the background is simply not there when\nreopening windows. I've asked this in QA here for more details:
\n\nhttp://developer.appcelerator.com/question/93591/background-disappe...
Here is some simplified code that reproduces the issue. This is\nthe entire app.js. Run this with 1.4.3 and the background will\nreturn to white after each cycle. Run with 1.5.2, and the screen\ngoes to black after the first click.
\n\nTitanium.UI.setBackgroundColor('#000');\n\n\nvar win1 = Titanium.UI.createWindow({ \n backgroundColor:'#000',\n exitOnClose:true,\n navBarHidden:true,\n orientationModes: [Ti.UI.PORTRAIT],\n zIndex:-1\n});\n\nwin1.open();\n\nvar win3 = Ti.UI.createWindow({backgroundColor:'#FFF'});\n\nvar button = Titanium.UI.createButton({\n title:'click to cycle',\n top:190,\n left:30,\n height:50,\n width:250,\n font:{fontSize:20}\n});\n\nwin3.add(button);\n\nwin3.open();\n\nbutton.addEventListener('click', function(){\n\nwin3.close();\nwin3.open();\n});\n(from [a1a9c2af2ac88a98c13baee4e64ef6e91891e4b7])\n[#2579 state:fixed-in-qa] processProperties\nexpects a clone of the properties to be passed. Values are removed\nby some specialized classes before sending the properties to their\nparent's processProperties. Note: This example works with open and\nclose in the same click handler because it's a lightweight window.\nTrying it with an Activity/heavyweight window has unpredictable\nside-effect due to having to create the new Activity. \nhttps://github.com/appcelerator/titanium_mobile/commit/a1a9c2af2ac8...
closed against Titanium SDK version: 1.6.0 (01/06/11 08:47\n8b2fd0e) G1 (1.6) droid 1 (2.2.1) emulator 2.1. checked ipod touch\n4gt 4.2.1
If I understood correctly the fix is included in the build\nlocated
\nhere:http://builds.appcelerator.com.s3.amazonaws.com/index.html
\nunder: Jan 6 2011 02:15 r8b2fd0e4
If so then the issue is still not resolved for me. The\nbackground is no longer black and is now correct however when I\nscroll up I can see the previous window behind the first.
There is no scroll region in that test. How are you \"scrolling\nup\"
I created the ticket someone else posted an example. Apparently\nthe example had a different issue than mine. Example code is\nbelow:
\napp.js
\n\nTitanium.UI.setBackgroundColor('#000');
\n
\n\n\n
\nvar win1 = Titanium.UI.createWindow({
\n
\n
\n\n\n\n\n\nbackgroundColor:'#000',\nexitOnClose:true,\nnavBarHidden:true,\norientationModes: [Ti.UI.PORTRAIT],\nzIndex:-1\n\n\n\n\n
\n});\n\n
\nwin1.open();\n\n
\nvar win3 = Titanium.UI.createWindow({\n\n
\ntitle: 'Window 3',\nname: 'Window 3',\nbackgroundColor: '#C4D5DA',\nfullscreen: false,\nanimate: ({opacity: 0,duration: 300 }),\nurl: 'win3.js'\n});\n\n\n\n\n\n
\nwin3.open();\n
win3.js
\nvar win3 = Titanium.UI.currentWindow;
\n
\n\n\n
\nvar body = Titanium.UI.createScrollView({
\n
\n\n\n\n\n\ncontentWidth:Titanium.Platform.displayCaps.platformWidth,contentHeight:500,\nright:0,left:0,top:60,bottom:50,width:'auto',height:'auto',\nshowHorizontalScrollIndicator:false,showVerticalScrollIndicator:false});\n\n\n\n\n
\nwin3.add(body)\n\n
\nvar button = Titanium.UI.createButton({\n\n
\ntitle:'click to cycle',\ntop:190,\nleft:30,\nheight:50,\nwidth:250,\nfont:{fontSize:20}\n\n\n\n\n\n
\n});\n\n
\nbody.add(button);\n\n
\nbutton.addEventListener('click', function(){\n\n
\nwin3.close();\nwin3.open();\n});</code>\n\n\n\n\n
\n
I apologize for the terrible formatting. I did preview my post\nbut was distracted by a work emergency before I could fix it. I was\nhoping to be able to edit it after the fact...
\nAlso, I will try putting my code into a single page and see if\nthat solves my problem.
I did create this issue but it seems there were multiple issues\nI was running into, should I create a new issue? (perhaps someone\nelse should who could define it more clearly...)
New ticket created here: \nhttps://appcelerator.lighthouseapp.com/projects/32238-titanium-mobi...