Title says it all really. It should be possible to expand a node and force the parent nodes, all the way up the tree to expand too. Likewise for Collapse. -- Stuart
At the moment when disabling a RadTreeNode on server/client side the complete node gets disabled with the CheckBox. We had a use case where we would like the node to stay functional (collapsable/expandable/clickable/hover-effect) but only the checkbox to become disabled. As this can't be achieved with the RadTreeView we had to build a work-around for that. Most likely people in need of this feature make a new HTML-variable to store/transmit/apply the state of the checkbox since the manipulation of the Checkboxes gets lost in a postback. This would have to be implemented as a server/client-feature as it is with the enabled/disabled-state of the RadTreeNode. Kind regards
I know that the doc's specifically say that it doesn't do this, but it should. Further both the server- and client- side events should fire. This is true of the RadTreeView as well as any of the newer controls that include a TreeView in their core functionality, (DropdownTree, TreeList).
ADD: Copy node on Drag And Drop TreeView
At the moment it is not possible to rebind the RadTreeView on the client if the datasource is changed when treeview is bound to a ClientDataSource or WebService. Scenarios: - Changed nodes on the server (database) cannot be refreshed on the client. - TreeView is populated based on a custom parameter value.
The ClientNodeClicking and server-side NodeClick events are triggered when tap-to-scroll the Treeview in Android (taphold event). Steps to reproduce: 1. Open http://demos.telerik.com/aspnet-ajax/treeview/examples/overview/defaultcs.aspx in mobile Chrome of Android device (or in Chrome emulator) 2. Tap over a node to Scroll the Treeview Result - the tapped node gets selected Expected - the Treeview detect the tap from holdtap events and the node is not selected when scrolling occurs
I think that TreeView incorrectly handles the case of a drop beneath a node that is expanded. When a node (with or without children) is _not_ expanded, then dropping directly beneath (meaning lower down on the page) that node indicates that the node should be made the next sibling of the node. - A + B ------ <- Drop indicator means that dropping here will cause the dropped node to be the next sibling of B, which makes sense. - C This case makes perfect sense. However, when the node is expanded, the drop indicator doesn't change it's behavior, and I think it should. - A + B ------ <--- Dropping here will cause the dropped node to be the next sibling of B, but this is not visually where it will appear in the tree. - B.1 - B.2 <--- This is where the node will appear after drop. - C This is counter-intuitive to most people. People think that dropping between B and B.1 would make the dropped item to become a child of B and a prior sibling of B.1. But instead, it has the same effect as if the B node wasn't expanded and adds the new dropped node as the next sibling of B. Note that in this case, the newly dropped node doesn't show up where it was dropped. When a node doesn't appear in the tree where it was dropped, people assume that that's a bug. To see the issue, go here: http://demos.telerik.com/aspnet-ajax/treeview/examples/functionality/draganddropnodes/defaultcs.aspx In the "RadTreeView1" treeview, try to drag the "Deleted Items" item to be the last item in the list (but not a child of "Search Folders"). If you drag toward the bottom of the tree, after you drag down past "Unread Mail", you see the drop indicator that shows that you can drop to make it be the next sibling of "Unread Mail". If you keep dragging down, you _don't_ see an indicator that you can drop to make the next sibling of "Search Folders". However, if you drag between "Search Folders" and "Form Follow Up", then you _will_ see an indicator that shows that the item will be made the next sibling of "Search Folders". And if you drop there, it will indeed be made the next sibling of "Search Folders", but of course it will appear at the bottom of the tree (not where you dropped it). The kendo TreeView has the same behavior as the RadTreeView. However, I have found some TreeViews that handle it in the way I would prefer. See http://mbraak.github.io/jqTree/ for an example.
It would be nice to have the ability to check/uncheck a range of consecutive check boxes in a tree view, for example by clicking the starting check box and shit-clicking the ending check box. I would like to check a range of nodes as shown in the attachment, without checking one at a time.
Hello, Please add support to bind to System.Dynamic.DynamicObject: https://msdn.microsoft.com/en-us/library/system.dynamic.dynamicobject%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396 Regards, Douw