thanks for the response. i think the bug, tersely described, is that setting a SurfaceView's visibility to GONE (or indeed INVISIBLE) should probably release any hold on the screen.
and yes -- my fix is to dynamically add and remove the relevant/offending views as their corresponding tabs become active and inactive etc. it's looking good but i'm seeing some side effects - calling VideoView.startPlayback() before the view is actually added to the layout results in no video. i'm trying to work around that ATM. >I'm sure this is an artifact of the way we handle video overlays - >they are treated differently than a regular surface. If I understand >the behavior, I would agree that it's a bug. > >As a workaround, you will probably need to tear down the VideoView. >For camera preview, you should be able to get away just clearing the >preview surface. > >On Dec 3, 5:36 pm, Jason Proctor <[EMAIL PROTECTED]> wrote: >> i'm looking at the source for TabHost and it turns out that when a >> tab is selected, its view is set to visibility GONE. hence me setting >> it to INVISIBLE afterwards probably isn't helping! >> >> either way, i think making a SurfaceView GONE should probably stop it >> claiming chunks of screen and interfering with other views which are >> definitely VISIBLE. >> >> does the panel agree that this is a bug? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
