02-18-2012 02:52 PM
Hi, I'm trying out the basic openGL based apps on playbook emulator and i have noticed that when the app windows is not fullscreen, the window does not appear as expected. This was true for sample openGL apps as well. I'd upload a screenshot but apparently i cant so i'll just describe it. Instead of displaying a mini version of the opengl app, it displays a blueish window with what looks like a hemisphere at the bottom.
So is there something i am doing wrong with the code or is it just a simulator limitation?
Solved! Go to Solution.
02-21-2012 04:12 AM
please guys i really need the answer to this one. Has anyone ever tried to run an opengl app on the simulator?
02-21-2012 09:50 AM
I am not seeing this behaviour on my Simulator.
02-21-2012 10:39 AM
02-21-2012 11:00 AM
I tried HelloWorld from samples.
02-21-2012 11:10 AM
02-21-2012 01:18 PM
Yes, the HelloWorld from the NDK is OpenGL. If you continue to experience issues please provide a screenshot of the issue, the sample being used as well as version of NDK and simulator OS being used.
Regards,
02-21-2012 01:44 PM
It turns out that the HelloWorld app we're talking about here is same as the 'sample app' im talking about, so now you know the code. I've Uploaded a screenshot of the minimised app on flickr, here's the link :http://www.flickr.com/photos/77137187@N05/69174894
The NDK is version 1.00 beta3
The simulator is version 2.0.0.7109
Thank you for taking the time to help me out ![]()
P.S.: I tried the same app on emulators on two pcs other than my own just to verify that it didnt have anything to do with my hardware but the result was the same.
02-21-2012 01:59 PM - last edited on 02-21-2012 02:00 PM
I should also add that this app doesnt play well with other apps that are open. for instance, when i minimise it and tap on the browser icon, then as soon as the browser becomes fullscreen, the opengl rendering of the said app is displayed as if it was the active app
I managed to stop this behavior by calling the render function only when the app was in fullscreen, but the original problem remained.
So should the app have been behaving that way?
02-21-2012 02:47 PM
I just reproduced the issue and it does appear to be a bug. Please post to Issue Tracker and I will escalate: