GWT: 2.5.1
Smart GWT: Smart GWT 4.1d SNAPSHOT_v9.1d_2013-07-23/LGPL
GWT env: Development and production mode
Browser: firefox 10ESR, firefox 20
OS: Windows 7 professional
some of the porperties set for list grid
ResultSet
I have a listgrid with 300 columns bound to a RESTDatasource. When the number of records is 1.5 million, the list display correctly. First 75 records are retrieved from server and user can scroll to the next or last page.
However, when the records increase to 2 million, the list display only 50+ records and there is no additional page to scroll.
There is no error except the warning in development mode.
[ERROR] [main] - 14:05:53.503:TMR3:WARN:GridBody:isc_ListGrid_2$51d:This grid is showing 2,819,890 rows. Due to native rendering limitations, grids with this many rows may not appear correctly on all browsers. Consider filtering the data displayed to the user to reduce the total number of rows displayed at a time. This will improve usability as well as avoiding unpredictable behavior.
However, i'm not displaying all the records at one so why is there a different behavior when the record increases?
Smart GWT: Smart GWT 4.1d SNAPSHOT_v9.1d_2013-07-23/LGPL
GWT env: Development and production mode
Browser: firefox 10ESR, firefox 20
OS: Windows 7 professional
some of the porperties set for list grid
Code:
setShowAllColumns(false); setShowAllRecords(false); setShowRowNumbers(true);
Code:
setFetchMode(FetchMode.PAGED);
However, when the records increase to 2 million, the list display only 50+ records and there is no additional page to scroll.
There is no error except the warning in development mode.
[ERROR] [main] - 14:05:53.503:TMR3:WARN:GridBody:isc_ListGrid_2$51d:This grid is showing 2,819,890 rows. Due to native rendering limitations, grids with this many rows may not appear correctly on all browsers. Consider filtering the data displayed to the user to reduce the total number of rows displayed at a time. This will improve usability as well as avoiding unpredictable behavior.
However, i'm not displaying all the records at one so why is there a different behavior when the record increases?
Comment