> Giving a little bump here... > Please help? If you're going to bump, quote yourself -- it makes it easier to answer questions.
I saw your original post, didn't really understand your questions, and so I let it go. Since you're asking again, here are my weak answers: "1. Is this a proper approach? or should I have a ListView for every Adapter?" That depends on whether you want to show the user seven ListViews at once. "2. Every time I re-use that ListView I just use setAdapter( adapter ) and it replaces any data with the new data. Is this a proper way to do it?" I do not know of any alternative, short of having multiple ListViews. "What about if one adapter requires a header view and than I place a new adapter to it? " You can't do that. You need to add headers/footers before adding an adapter, according to the documentation. This would be one scenario where you might need to have multiple ListViews and only show one at a time (e.g., via setVisibility()). However, your overall approach seems very memory intensive, depending on how many rows your adapters have. Knowing nothing about your application, it feels like you are trying to do too much in one activity, work that should be split over several activities. But, again, I do not know your application, so that advice may well be faulty. -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
