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.
Basically I want to populate a ViewFlipper with some views when an AsyncTask has been completed. Rather than hiding the views somewhere in my layout with the visibility set to ‘gone’, I thought I’d just inflate them from a different layout XML-file on my AsyncTask completion.
Basically the Views just contain some ViewGroups with some text and pictures in them, nothing big. Question is, is this still a bad idea resource-consumption wise?
I’d say it’s better, because the activity’s initial layout will be smaller (and thus faster to load). The downside is that inflating the view will probably be slightly slower than just making it visible. Note that lists in Android work this way : a few list elements are inflated when needed, and then recycled. Just avoid inflating the same things over and over again.
A nice alternative to this could be using a ViewStub. It does pretty much what you want to do : it doesn’t load the layout until you set it’s visibility to Visible.
And as for the AsyncTask, be sure to do that work in the onPostExecute method, as it runs on the main UI thread, and you can’t manipulate your Views from another thread.