Please provide an option that allows exposing the TreeView nodes' indexes. Such a feature will be especially helpful when rearranging the TreeView nodes by dragging.
[isDisabled]="disabled || isDisabled(node, nodeIndex(index))"
Because of the hardcoded disabled property, isDisabled cannot be reliably used to control which item is disabled.
Disabling the parent node automatically disables the entire tree under it and isDisabled is never called for those items.
It should behave like other functions - isChecked, isExpanded, isVisible etc - where you have full control over which item does what.
The tree view enables us to drag and drop one item at a time. we have a scenario where i want to drag and drop multiple items. tree view also enables multiple selection of items but not supporting drag and drop of multiple items. Could you please provide some solution to dag and drop multiple items
Please provide an optional callback function when rebindChildren has finished and the tree is stable again.
Do You have plans, to provide extended 'desktop-like' multiselection of nodes with ctrl/meta or shift key pressed?
My suggestion for the Angular treeview is to expose a doubleClick event, as opposed to just the single click event (or the selection node event). This would help in preventing events from firing unless the user has double clicked a node (as an option).
There is a filternodes option available but not with checkboxes. Would be glad to have Treeview filter(with checkboxes) something similar kenod jquery component(attached the link and screenshot for your reference). Is there any plans to release this feature in near future?
Please provide a built - in feature that allows to achieve the behavior demonstrated at the following link:
We are facing a notable poor performance in tree view when loading about 1500 tree nodes with custom template and it is taking approximately 32 Seconds to load it. You have already provided load more option to virtualize data but this is not so user friendly and suggested listview which has virtualization also not good fit to replace treeview. I wonder how this virtual scroll is missed in tree view!!. It is very important component to our project If you could provide this feature will be great.
I'm aware of the solution described https://www.telerik.com/forums/is-there-a-way-to-set-a-treeview-busy-like-grid's-loading but it would be nice to have a way to control build-in loading indicator instead of implementing a custom one.
In a scenario when the data is stored in the state and fetch children immediately returns empty observable and then when data is available and emitted to the source observable you can't see the loading indicator.
Click to expand a category, the "expand" icon is changed to "expanded" but no data is available yet. Two seconds later when data arrives it looks fine, but it would be really good to improve users experience and show a build-in loading indicator while data is not yet available
If you expand a tree node with 1000 items in it, and that tree has an ng-template the performance is very poor. It takes 7 seconds on my machine, see here https://www.telerik.com/forums/slow-treeview-with-large-datasets Please add virtualisation to the TreeView so that not so many DOM elements (and therefore ng-templates) need to be created.