Hi,
I'm sorry, but I made a stupid mistake. I set both row data and row count
within on RangeChanged, but I only used the (correct) user filter when
fetching the row data via RPC call. When fetching the row count via RPC
call I used a new, empty user filter, so the count was wrong.
Sorry for
Hello,
when I add a delay of 1 sec before the reload it works.
So there must still be some sync problem...
What can I test next?
Magnus
-
public void setFilter (UserFilter flt)
{
sel.setFilter(flt);
this.flt = flt;
//reload ();
delayedReload ();
}
public void delayedReload
Hi,
I found out the following:
When the second call to onRangeChanged occurrs, there are fewer records in
the list than visible rows in the CellTable!
The first rows are updated correctly, but the remaining visible rows are
not cleared!
So there is probably no synchronization problem, but a
You should call updateRowCount if the row count changes (such as when
applying a filter)
On Sunday, August 26, 2012 3:42:26 PM UTC+2, Magnus wrote:
Hi,
I found out the following:
When the second call to onRangeChanged occurrs, there are fewer records in
the list than visible rows in the
Hi Thomas,
I tried to modify the reload method like this, but without success:
public void reload ()
{
pvd.updateRowCount (0,true); // avoid to many visible rows
Range r = tbl.getVisibleRange();
tbl.setVisibleRangeAndClearData (r,true);
loadRecordCount (); // asynchronously load
I have a similar post. I was trying to do something as simple as when
I click on a refresh button to completely clear my provider and
display the freshly received entities from the server. I haven't had
time to go back and look at it, but I would also be interested in
getting a definitive idea as
Hello,
I found this interesting article:
http://turbomanage.wordpress.com/2011/03/02/gwt-2-2-asyncdataprovider-celltable-gotcha/
It also states that one should always update both row count and row data.
But when looking to the code in the article, it seems that the author
assumes that
