Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Do I need to load my custom ListAdapter in another thread? I have done so previously, but I also downloaded the data in that same thread.
Are there any pros or cons to loading a ListAdapter with or without a thread? Is loading a thread that resource intensive?
Yes, if your list has anything more than a trivial amount of entries in it or you’re getting anything off of the network or from disk, you should be loading them on a separate thread. But it’s actually really easy to do this with the new Loader classes. They were basically made for this kind of stuff. They’ll take care of doing all the loading stuff on a separate thread without you having to mess with all the nasty threading stuff. You just tell it what you want to load and it takes care of doing the stuff in the background for you.
Note that while the Loader classes weren’t introduced until API-11, you can still access them from API-5 and up using the android Support Package.
It sounds like for your case in particular, you should use an AsyncTaskLoader.