The Android List views are optimized by not creating the new UI objects for n number of rows and reusing the Objects with different data. But how can we develop this optimized lists, when coming to the different row views and designs?
Share
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.
The Android List views are optimized by not creating the new UI objects for n number of rows and reusing the Objects with different data. But how can we develop this optimized lists, when coming to the different row views and designs?
You need to override getItemViewType() in your adapter and return different values for different row views. The ListView is smart enough to pass different views in
getView()for different view types.