As I'm thinking of this more, the view also must respect given
pageSize nd dataSize. Therefore to have view/table 0 rows high when
the view is set to pageSize=15 and thinks dataSize=1156 would be kinda
'uncertain'. The table would have to display empty row, or rows, and
they would have identical (~'empty') key, which would be quite mess.
Clearing a view makes probably sense only in conjunction with setting
dataSize=0. (Hopefully it works, too late to test that now though.)
Seems like I should reconsider that original approach. My apologies
for this monologue! :P
On Jun 14, 2:06 am, Jaroslav Záruba <
jaroslav.zar...@gmail.com> wrote:
> Hello
>
> I assume the proper way to manipulate data in views without a round-trip to
> server* would be to call:
> AsyncListViewAdapter<T>.updateViewData(int start, int length, List<T>
> values);
> But that does nothing when I try to *clear* the data:
> AsyncListViewAdapter<T>.updateViewData(0, 0, new ArrayList<T>());
>
> Looking at AbstractListViewAdapter<T>.updateViewData<
http://code.google.com/p/google-web-toolkit/source/browse/branches/2....>it