Announcement

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

    onScroll down ListGrid leave 5-6 rows blank or may be leaving space

    Hello,

    I have runtime generated ListGrid, which loads data from server. I display 100 rows at a time and then onScroll more data are loaded.
    Can you please suggest, why ListGrid leave 5-6 rows space above and below??

    Please find image.
    Click image for larger version

Name:	scrollup_spacedown.PNG
Views:	117
Size:	18.3 KB
ID:	234656
    Scrolling up, have leave space down and Scrolling Down, have leave space up


    Click image for larger version

Name:	scrollDown_spaceup.PNG
Views:	118
Size:	42.4 KB
ID:	234657



    Thanking you.

    #2
    You need to include your SmartClient version as it mentioned under "Create New Topic":

    1. The *complete* SmartGWT or SmartClient version from the lower left-hand corner of the Developer Console (see FAQ for how to open Developer Console), for example, "v10.0p_2015-06-18/PowerEdition Deployment"

    Comment


      #3
      Note that, although your post incomplete, the result you are showing is almost certainly due to third-party CSS included in your page. See the FAQ about this.

      Comment


        #4
        Thank you. I found a related post to this problem and that works for me.

        "This is by design. When using incremental rendering with variable height records, there is no way to know how many records would appear in the last viewport, so this blank space must exist at the end.

        To avoid, either set fixed heights for all records, or turn off incremental rendering; the latter only works for small datasets."

        I set below property.

        fixedRecordHeights: true,


        Please find reference below. I am using SmartClient 10.0, but GWT and SmartClient both have same solution.

        http://forums.smartclient.com/forum/...area-at-bottom

        Thanks a lot.

        Comment


          #5
          Virtual scrolling explains your first but not your second screenshot, that's why we didn't bring it up.

          Because of your second screenshot, the explanation is again most likely third party CSS.

          Comment

          Working...
          X