If you would like to animate your transitions, where one list slides out and second slides in, all you need is two listviews. And in your activity, you would need to keep track of one that is currently visible, and the other one, that is invisible. When there comes a point that you need to switch listviews, your logic becomes something like this:
ListView oldView = this.currentList; ListView incomingView = this.invisibleList; this.currentList = incommingList; this.invisibleList = oldView; this.slideOutAnimation.setAnimationListener( .. code here, onAnimationEnd(oldView.setVisibility(View.GONE)); incomingView.setVisiblity(View.VISIBLE); incomingView.startAnimation(this.slidInAnimation); oldView.startAnimation(this.slideOutAnimation); On Jul 11, 10:35 am, Moto <[email protected]> wrote: > The reason for this post was to use one ListView for multiple adapters > because I thought it would help decrease the level of complexity my > xml layout would have, therefore starting my activity much faster. > Apparently it's not such a good idea. > > As of now, if this matters anyways, my fatty Activity uses at most 70% > of the given 3.9MB Heap size. > > Thanks Mark and well I'll take into consideration your ideas and try > to make it one slim and faster Activity. > > Thanks, > Moto! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
