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 GLSurfaceView. It starts another child-activity, with Theme.Dialog, that is partially transparent: Activity *DialogA*. When *DialogA *becomes visible, the *GLA*'s* *onPause is called. If *GLA *then calls glSurfaceView.onPause(), the contents of *GLA *that is still partially visible around *DialogA *may become invalid (it may turn transparent/black). If *GLA *calls glSurfaceView.onPause() in its *onStop* method instead, you're at least sure that the child-activity is not partially transparent and covers the entire screen s that the glSurfaceView is entirely hidden and glSurfaceView.onPause() can be called safely without any visual side effects. My question is: *Is it safe to call glSurfaceView.onPause() in an activity's onStop method (and glSurfaceView.onResume() in its onStart method)?* *If not, what bugs/side-effects can I expect? * *If not, how can I handle partially transparent child-activities the correct way?* * * Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
