Hi guys,
SmartClient is the best open source enterprise RIA out there - well done.
I've recently upgraded to use SC 11.
In SmartClient_v110p_2016-04-21_LGPL, I note that when drag scrolling (with the scrollbar thumb) in a paged list grid, a lot of and perhaps excessive server requests are made (using a rest data source in paged mode).
After doing a little bit of poking I tried setting fetchDelay on dataProperties like so..
dataProperties: {
fetchDelay: 100, // need to delay and queue up fetches when using the scroll bar handle
}
within my listgrid constructor.
This didn't work.
I also noticed that fetchDelay was always 1 by the time ResultSet.getRange() was called via
dataProperties: {
fetchDelay: 100, // need to delay and queue up fetches when using the scroll bar handle
getRange : function (start, end, ignoreCache, fetchNow) {
console.log(start + ' : ' + end + " : " + ignoreCache + " : " + fetchNow + " : " + this.fetchDelay);
return this.Super('getRange', arguments);
},
which gave me a tonne of output like
0 : 51 : undefined : undefined : 1
So I ended up setting fetch delay before my call to this.Super('getRange', arguments); and this had the desired effect.
Perhaps a bug?
Was there a deliberate change from SC 10.1 to SC 11 in the delay?
Thanks in advance,
Mike.
SmartClient is the best open source enterprise RIA out there - well done.
I've recently upgraded to use SC 11.
In SmartClient_v110p_2016-04-21_LGPL, I note that when drag scrolling (with the scrollbar thumb) in a paged list grid, a lot of and perhaps excessive server requests are made (using a rest data source in paged mode).
After doing a little bit of poking I tried setting fetchDelay on dataProperties like so..
dataProperties: {
fetchDelay: 100, // need to delay and queue up fetches when using the scroll bar handle
}
within my listgrid constructor.
This didn't work.
I also noticed that fetchDelay was always 1 by the time ResultSet.getRange() was called via
dataProperties: {
fetchDelay: 100, // need to delay and queue up fetches when using the scroll bar handle
getRange : function (start, end, ignoreCache, fetchNow) {
console.log(start + ' : ' + end + " : " + ignoreCache + " : " + fetchNow + " : " + this.fetchDelay);
return this.Super('getRange', arguments);
},
which gave me a tonne of output like
0 : 51 : undefined : undefined : 1
So I ended up setting fetch delay before my call to this.Super('getRange', arguments); and this had the desired effect.
Perhaps a bug?
Was there a deliberate change from SC 10.1 to SC 11 in the delay?
Thanks in advance,
Mike.
Comment