There could well be a bug here, nobody has done this kind of thing as far as I know, and the code for handling a SurfaceView is quite complicated and could easily have bugs in this area.
So feel free to file a bug. That said, I can't make any promises about this being addressed any time soon, as there are probably many features and bugs that at this point have a significantly higher priority. If it is something that someone really wants to have fixed, the best way to get a result on it would probably be to debug the platform and submit a patch to fix it. :} (Which I know is asking a lot, because this IS very tricky code.) Oh one other thing, you might want to use hierarchyviewer just to make sure the state of your view hierarchy looks sane. On Wed, Dec 3, 2008 at 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? > > > > > -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
