Hello all,
I've been working through various quirks with the igTree and drag and drop, but have found one that is a huge pain. When dropping a node onto another node, it's added as a child correctly. However, when dragging this node (with a new child) onto another node, the node is collapsed. When expanding, rather than display the node that was previously added, it re-retrieves the data from the server, which of course is inaccurate.
This seems needless, in that when the drop event occurs, the actual dragged element still has all of its children available in the markup. I've tried catching the collapsing event for the dragged node but that event never fires.
Now I'm looking at a cumbersome server-side management of tree changes and applying them to any populate requests. This is far from ideal.
Has anyone else had any experience with this?
(also, there's strange behavior where upon dragging a node to its parent, the node simply disappears, but for the time being I've just disabled this as a drop target)
Thanks
You can take any "load on demand" sample that is on the site, and enable drag + drop.
You can drag / drop to any of the nodes, but when you drag the node with the new children to another node, it will collapse it, and re-retrieve on expand, which gets the original server side data, without the children that were added to it.
Please let me know if you are able to reproduce.
Hi there,
I will create a customer case for you. Could you assist our developer support by providing them with a small sample isolating the issues that you're experiencing and providing the steps to reproduce.
Thank you for using the Infragistics forums!