Searching the net and this group I can see this topic has come in a
billion times.
What I wanted to know if anyone can explain or point to information on
how the View/getView() implementation determines the number of
getView() calls that are required to display content.

I understand there are performance tweaks that can be done to
streamline code such as using the convertView passed in with getView.
But just to put my curiosity to rest I would like to know how all
these getView() calls works. :-)

In my own program I have one listview of information that has :
25 rows of content, 3 visible and getView() is called about 4 times

I have a different listview of information that has:
10 rows of content, 6 visible and getView() is called about 60 times

>From what I have read in this group and on the net, the number of
getView() calls can be determined by layout_weight and/or the grouping
of parent/child views in your activity. (I think)

So I am just looking for a deeper explanation here. Maybe I can design
my app in a better way to avoid any design flaws I may have.

Thanks!

-- 
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

Reply via email to