[FNR] Aggregation row and LazyRowRender bug

[keygen]

We have a Grid and a ListStore with a ListLoader. We make a request to the server and build the grid with an aggregation field. When the data were downloaded faster than the grid is rendered, then the aggregation field is calculated incorrectly.

- gxt 2.2.4, gwt 2.3

- Sample code

public class Test2 implements EntryPoint {

	@Override
	public void onModuleLoad() {
		
		BaseModelData model1 = new BaseModelData();
		model1.set("number", 1);
		BaseModelData model2 = new BaseModelData();
		model2.set("number", 2);
		final ArrayList<BaseModelData> result = new ArrayList<BaseModelData>(Arrays.asList(model1,model2));
		
		ListStore<BaseModelData> store = new ListStore<BaseModelData>(new BaseListLoader<ListLoadResult<?>>(
				new DataProxy<List<BaseModelData>>() {
			@Override
			// emulating an asynchronous HTTP request
			public void load(DataReader<List<BaseModelData>> reader,Object loadConfig,final AsyncCallback<List<BaseModelData>> callback) {
				Scheduler.get().scheduleDeferred(new ScheduledCommand() {
					@Override
					public void execute() {
						callback.onSuccess(result);
					}
				});
			}
		}));
		
		store.getLoader().load(); // send request
		
		ColumnConfig columnConfig = new ColumnConfig("text","text",100);
		ColumnConfig columnConfig2 = new ColumnConfig("number","Number",100);
		
		ColumnModel cm = new ColumnModel(Arrays.asList(columnConfig,columnConfig2));
		AggregationRowConfig<BaseModelData> row = new AggregationRowConfig<BaseModelData>();
		row.setHtml("text", "Total");
		row.setSummaryType("number", SummaryType.SUM);
		row.setSummaryFormat("number", NumberFormat.getDecimalFormat());
		cm.addAggregationRow(row);
		
		Grid<BaseModelData> grid = new Grid<BaseModelData>(store, cm);
		grid.setPixelSize(500, 500);
		
		// workaround
		// grid.setLazyRowRender(0);  
		
		RootPanel.get().add(grid);
	}

}

[sven]

This is now fixed in SVN as of revision 2399

[pseudogxt]

Hello,

this fix is not in 2.2.4. Right?
Is there a workaround for 2.2.4?
I can not wait until the next release, i have to fix the bug now.

Please help!
Thx!

[sven]

this fix is not in 2.2.4. Right?

Correct, as this was reported and fixed after the GXT 2.2.4 release.

Is there a workaround for 2.2.4?

There is no public workaround available. If you have a support subscription you can get the latest code out of SVN.

[pseudogxt]

No 2.2.5 ?

[sven]

There will be a 2.2.5 release also, but please note that normally patch release are only for support subscription holders.

[pseudogxt]

One week, one month, ...?

[sven]

There are no public release dates for the next release.