Announcement

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

    dataFetchDelay in paged TreeGrid without impact

    Hi there,
    We have a huge Treegrid with thousands of treenodes. We have implemented the paged treegrid and it's working fine.
    The reason why we area using the paged treegrid is to decrease loading time for the user. Loading new data needs sometime longer time, about 1 second.
    So if the user is scrolling through the tree, the tree starts a lot of requests parallel so the load of the server increases dramatically. with increased load also the reponsetime can increase. So even if the first request is answered in 500 ms the last one (of 30 requests) could need 15 seconds.

    As I'm reading the docs the "dataFetchDelay" can be used to minimize the amount of requests. Or at least increase the time before the treegrid loads the specific shown data.
    But in the example below the property does not have any effect.
    Is there a way to increase the the delay before a dataFetch, so the treegrid waits longer if the user stops scrolling? Isn't that the dataFetchDelay?

    See here: http://www.smartclient.com/smartclie...sizeIncrease=4
    Here you can see that a fast scrolling does resutl into 34 requests


    In the example below the given attribute "dataFetchDelay" doesn't have any impact.
    Code:
    isc.TreeGrid.create({
        dataSource: "hugeTree",
        dataFetchMode: "paged",
        autoFetchData: true,
        showFilterEditor: true,
    dataFetchDelay: 2000,
        // customize appearance
        fields: [{ name: "name", canFilter: true }],
        width: 500,
        height: 400,
        showOpenIcons: false,
        showDropIcons: false,
        nodeIcon: "pieces/16/cube_blue.png",
        folderIcon: "pieces/16/cubes_blue.png",
        closedIconSuffix: "",
        showConnectors: true
    });
    Best regards

    #2
    We see the behavior you reported and are looking into a solution.

    Comment


      #3
      This has been fixed for SC 10.0p and newer releases, and the fix should be in the nightly builds dated 2017-08-08 and beyond.

      Comment


        #4
        Thanks, I can confirm the fix :-)

        Comment

        Working...
        X