I switched my screenshot code to using captureScreen and it’s callback.
It’s working fine (and way faster then the old screenshot code), but while testing it on a Nexus 9 last night, it hang my game. I never got a reply, and I think I wasn’t even getting any updates to my game cycle anymore.
I rebooted the device, started my game, same thing happened.
I then booted up my Nexus 7, updated my game to the latest version (with the new screenshot code) and it worked fine. I had already tested it on a Samsung Galaxy Tab 2 which worked fine as well.
So I figured it had to be something nexus 9 specific, but it was late and I went to bed
This morning, I tried it on the Nexus 9, and it worked fine…
So I’m happy that it’s working, yet it still feels “scary” that it didn’t work the night before.
Has anyone had issues with the captureScreen code? Is there a way the code can fail without ever calling the callback funtion, for example by ending up in an infinite loop (because that is what it looked like).
I looked at onCaptureScreen in ccUtils, but I don’t see anyway that could hang anything…
@MFHSchoonbrood i also have a problem, when i save a render target to the phone library on android , the saved image it’s empty(black) ,but it worked fine in the ios devices, please help me .