Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    ListGrid unable to consistently calculate scrollable height when using getRowHeight

    Hi Isomorphic,

    If I start from this example:
    https://www.smartclient.com/smartcli...izeIncrease=10

    and use this code:
    Code:
    isc.ListGrid.create({
        ID:"dsListGrid",
        width: "100%",
        height: "100%",
        autoFetchData: true,
        dataSource: "supplyItem",
        getRowHeight: function(record,rowNum){
            if(!record || record.isFolder){
                return this.cellHeight;
            } else {
                return 150;
            }
        },
        canMultiGroup: true,
        canGroupBy: true,
        groupTitleField: "category",
        groupStartOpen: "all",
        showGroupSummaryInHeader: true,
        showGroupTitleColumn: false,
        groupByMaxRecords:5000,
        groupByField:"category",
        showAllRecords: false,
        drawAheadRatio:5,
        showGridSummary: true,
        showGroupSummary: true,
    });
    Then the ListGrid has problem scrolling at the bottom of the table. As the attached gif demonstrates, when I get to the bottom of the scrollbar, it just displays a white background (i.e., not the normal checkered background). The problem seems tied to my use of getRowHeight. I would use cellHeight, but then my group rows are extra tall too (which I don't want).

    What I couldn't show in the gif due to the forum's file size restrictions was that if I scroll up to the data and then back down again to the bottom, I still get the white background. Sometimes if I scroll to the bottom "carefully", the last row is at the bottom, but other times, at least in my real code, it seems like it can never find the bottom correctly.

    Is there a configuration parameter I couldn't find?

    Thanks,
    Amos.

    I'm using Chrome 63.



    Click image for larger version  Name:	Dec-13-2017 10-47-34.gif Views:	1 Size:	146.1 KB ID:	250826
    Last edited by nitroamos; 13 Dec 2017, 08:06.

    #2
    This should be fixed in SC 10.0 and newer releases in todays builds, labeled 2017-12-15.

    Comment


      #3
      I neglected to acknowledge that this fix works. Thanks!

      Comment

      Working...
      X