Re: [android-developers] GLSurfaceView's onPause and onResume called in Activity's onStop and onStart to handle partially transparent child-activities. Is this OK?

2011-10-03 Thread Streets Of Boston
We did a proof on concept (we actually have implemented it) before asking this question. You can actually remove the calls to GLSurfaceView.onPause and GLSurfaceView.onResume entirely and most of the time it will work. Leaving these calls out will fail only after *excessive *rotations/configur

Re: [android-developers] GLSurfaceView's onPause and onResume called in Activity's onStop and onStart to handle partially transparent child-activities. Is this OK?

2011-10-03 Thread Christopher Van Kirk
I'm not sure why you're asking this question. It seems like a fairly simple thing to set up. Why not just try it and see? My guess is that it won't work because your activity hasn't been given a Surface yet, and GLSurfaceView depends on having a surface to draw on, obviously. But again, I thin

[android-developers] GLSurfaceView's onPause and onResume called in Activity's onStop and onStart to handle partially transparent child-activities. Is this OK?

2011-09-27 Thread Streets Of Boston
The documentation of GLSurfaceView states that its onPause and onResume should be called when its Activity is paused (onPause) and resumed (onResume). Can it be called in onStop and onStart instead to be able to handle partially transparent child-activities. Say: Activity *GLA *has a GLSurfaceV