The alternative would be, if I understand your question correctly, to have one listadapter that takes data from various sources, depending on some variable that is set. Your app would prepare the various sources of data independently, and the getView in your listadapter determines which of the sources is used at what time. I think that would be less complex than having a number of list adapters on one listview in one Activity. But again, I may misinterpret your question.
On Jul 11, 7:35 pm, 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 -~----------~----~----~----~------~----~------~--~---
