Fyi, I would guess the problem has to do with loading and initializing your view hierarchy, and not with the previous surface view. Have you tried launching with just the second hierarchy and not the surface view to see how fast it is?
On Tue, Jun 23, 2009 at 4:44 PM, skink <[email protected]> wrote: > > > > On 23 Cze, 22:09, Dave Bordoley <[email protected]> wrote: > > Why not use one View resource which includes both the SurfaceView for > > the animation and the normal view and show/hide them using > > setVisibility(View.GONE) and setVisibility(View.VISIBLE). This is > > pretty quick and how I've done something similar in the past. > > > > Dave > > > > thanks Dave, > > i'll try your approach > > did you use FrameLayout as a container for both Views? > > pskink > > > -- 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, and so won't reply to such e-mails. 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 -~----------~----~----~----~------~----~------~--~---
