That's how ListView works :) You just cannot make ANY assumption about how
many times getView/bindView is called in your adapter, and you cannot make
any assumption about the order of the calls.
On Tue, Nov 9, 2010 at 9:37 AM, bobetko wrote:
> I will reply to myself on this one...
>
> I learned
I will reply to myself on this one...
I learned that if I set my list's layout_height to WRAP_CONTENT, the
problem is no more. Wonder why?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-develop
On Tue, Aug 10, 2010 at 8:25 PM, Open wrote:
> I'm seeing the same thing and wondering the same. In my case I'm
> fetching an internet resource in setViewValues so calling it three
> times is very expensive.
Do not do network I/O on the main application thread. Do that work in
an AsyncTask.
>> I
That's probably because your ListView has a height set to
wrap_content. Which is a bad idea. Also, there is absolutely NO
guarantee that getView() will be called only once per item or in the
right order.
On Tue, Aug 10, 2010 at 5:25 PM, Open wrote:
> I'm seeing the same thing and wondering the sa
I'm seeing the same thing and wondering the same. In my case I'm
fetching an internet resource in setViewValues so calling it three
times is very expensive.
On Jul 30, 3:39 pm, William Ferguson
wrote:
> Hi all, I have a ListView populated using a SimpleCursorAdapter that
> has a ViewBinder, and
5 matches
Mail list logo
