Thanks for the inputs. I will try these and let you know.

Thanks for your response. We solved it by generating a unique id for the node being appended. thanks

Do you have any jsfiddle examples I can edit and show you?

Any response to this?

scrolling the selected row into view is ok, but why does it have to bring the node below it partially into view ?
That is the problem I am facing, because the double click on that selected node is getting triggered on the node below it.

multiSelect in treeGrid generally works great, but when we use the shift select feature for 1000 files it takes 10 seconds and for 2000 files 17 seconds.
Can you please suggest a workaround for this?

[finder.getTr]

We have a scenario where we delete few rows/nodes and then create a new node.
The treegrid('beginEdit') function ends up editing the existing row/node instead of the new one being created.

This happens only when we delete a node. Otherwise creating a new node works great using append followed by beginEdit functions in treegrid.

It looks like the finder.getTr function in datagrid component is still using the old html table when it finds the target node for editing.


Can you please fix it?

Still the same issue, this is reproducible only when the grid has vertical scrollbar visible (more rows below the last row being  selected).
The last row when fully visible should not bring jump upwards ideally and need not bring the row below it partially into the view

Thank you that fixed the problem. Do you forward port these fixes to the next version? Meaning if you release 1.5.2 , will you include this patch changes in that version?

You know what, I think this bug I am talking about is introduced in your patch that you guys provided for this topic to me.

http://www.jeasyui.com/forum/index.php?topic=6425.0

Can you please fix it. It is a serious issue.

[Dynamic Loading in TreeGrid]

When there is scrollbar on a treegrid and select the last row, it shifts the last row upward and partly shows the row below that.
In normal cases it is ok. But when we added double click feature to the rows, the row below the selected row is being selected when we double click the last row (especially when the second half of the rows being selected is used as double click area).
On your Demo pages of treegrid (http://www.jeasyui.com/demo/main/index.php?plugin=TreeGrid&theme=default&dir=ltr&pitem=) this can be reproduced using Dynamic Loading in TreeGrid example.

Can you fix it please?

That worked well. Thanks.
Do you forward port these fixes to the next versions?

After applying your patch, the sorting is broken. After expanding a node if I sort, all the children in the expanded node are removed from the parent node and are added as the siblings of the expanded node. May be the fix that you gave has broken the sorting as well.

Thanks for the fix, but it has introduced some bug in the case of remoteLoading
It is resulting in JS error when I am expanding any nodes. it is a remote load using ajax call.
Here is the image containing the info about line of code having problem.
https://drive.google.com/open?id=0B0okAKC9EloCTWM0QUZnVkRjQVU

The error in the console is as follows.
@ jquery-min.js:6
2017-01-09 13:57:41.406 jquery.easyui.min.js:formatted:15278Uncaught TypeError: Cannot read property 'length' of undefined
    at Object._98c (jquery.easyui.min.js:formatted:15278)
    at Object.render (jquery.easyui.min.js:formatted:15273)
    at _91f (jquery.easyui.min.js:formatted:14602)
    at jquery.easyui.min.js:formatted:14660
    at child.<anonymous> (Tree.js?version=@svn.revision@:43)
    at c (jquery-min.js:4)
    at Object.fireWith [as resolveWith] (jquery-min.js:4)
    at k (jquery-min.js:6)
    at XMLHttpRequest.r (jquery-min.js:6)

Here is the problem which was earlier posted by one of the other members
http://www.jeasyui.com/forum/index.php?topic=6223.0

I applied this patch and still I am seeing the same problem.