When doing a display.save() in a scene, pressing home button on Android and resuming into app, the whole screen is black, all controls except native textfield are away.
yep / ditto / exactly. it seems that display.save leaves some “remnant” in the display hierarchy, and on resume it tries to restore, but fails. result = black screen you can’t remove (display.save returns no handle) except close/restart app.
just a couple days ago tweeted a workaround that seems to fix it for me. don’t directly do display.save; instead do display.capture, grabbing the returned handle, then display.save that capture, then display.remove it.
that’s as far as the workaround goes - tho i suppose you could try hiding all OTHER elements just prior to captureBounds? (might be a lot of work, depending on how your code is structured)
time to file a bug? i can at least confirm that it’s “not just you”
When an app is suspended, the Android OS removes all OpenGL textures from memory. When the app is resumed, Corona must reload all images, but the capture image no longer exists in memory. You can’t use the display.save() function in Android applicationSuspend and applicationExit events because there are no OpenGL textures in memory to save.
When you do a display.save() and suspend the app after a while and resume it, the whole screen is black.Corona did not load anything, no controls, nothing.
The save works fine and I have my picture saved locally. But - as said - after a call to display.save() we got the issue.
yep / ditto / exactly. it seems that display.save leaves some “remnant” in the display hierarchy, and on resume it tries to restore, but fails. result = black screen you can’t remove (display.save returns no handle) except close/restart app.
just a couple days ago tweeted a workaround that seems to fix it for me. don’t directly do display.save; instead do display.capture, grabbing the returned handle, then display.save that capture, then display.remove it.
that’s as far as the workaround goes - tho i suppose you could try hiding all OTHER elements just prior to captureBounds? (might be a lot of work, depending on how your code is structured)
time to file a bug? i can at least confirm that it’s “not just you”
When an app is suspended, the Android OS removes all OpenGL textures from memory. When the app is resumed, Corona must reload all images, but the capture image no longer exists in memory. You can’t use the display.save() function in Android applicationSuspend and applicationExit events because there are no OpenGL textures in memory to save.
When you do a display.save() and suspend the app after a while and resume it, the whole screen is black.Corona did not load anything, no controls, nothing.
The save works fine and I have my picture saved locally. But - as said - after a call to display.save() we got the issue.