When using binding to CheckState property and TriStateMode is enabled the checking of parent (its business object) does not affect unrealized childrens' CheckState, because the bindings have greater priority than the TriState logic. Same in the other direction - checking the child has no effect over the parent. Marking this as Declined. TriState Mode is supported in XAML-defined or code behind defined trees with direct creation of 3Viewitems. In DataBound scenarios, 3-State should be created by the user with ViewModels as described in this help article. http://www.telerik.com/help/wpf/radtreeview-howto-tri-state-mvvm.html
a) Using WCF RIA Services b) Using QueryableDomainServiceCollectionView c) Using TreeView with above two d) Including LoadOnDemand e) Using "Prepared Item"
Ability to have both static and bound RadTreeViewItems or different hierarchy levels. Reason for decline: There is no proper way this to be implemented. This would require huge refactoring of the DragDrop, Styling, Editing, Virtualization logic. Complexity of such task is close to writing a new control from scratch.
Currently the CheckedItems collection contains items with CheckState "Indeterminate". The change can be controlled somehow since the modifying the behavior now will be a breaking change. Please avoid using this collection, it is has never been implemented completely. In DataBound scenarios, add CheckBox in ItemTemplate like it is shown in this help article. http://docs.telerik.com/devtools/wpf/controls/radtreeview/how-to/howto-tri-state-mvvm.html
Ability to temporary view particular element as root item. Functionality have to be similar to "View this as root" in the Solution Navigator window in Productivity Power Tools for Visual Studio. This is too custom requirement that can be implemented as application logic. Setting fildetered itemssource and preserving the current itemssource could be a possible solution.
It was suggested that the ItemTemplates in the tree view should update when the item template selector or the item template is changed. This will be hard to implement properly because of the numerous ways in which a template can be set. A naive implementation is more doable, though we are not notified when the ItemTemplate property changes ==== Reason for marking this Declined: Too little information, too old item (5.5 years) with too litle votes.
Allow selecting and unselecting items on right click when the SelectionMode is Multiple/Extended. Reason for decline: This can easily be implemented as application logc using th MouseRightButtonDown event of the RadTreeView.
Programmatically reorder items with animation. Declined. This could be implemented as application logic. The requirement is too specific to be included in the publi API of the RadTreeView.
The request is related to the method AddItemByPath - To build the whole hierarchy not only to add the string after last separator. Too specific requirement that could be implemented as application logic.
RadTreeView is throwing an IndexOutOfRangeException when the host panel is resized. StackTrace: at Telerik.Windows.Controls.TreeView.IndexTree.CumulativeValue(Int32 endIndex) in c:\TB\105\WPF_Scrum\Release_WPF\Sources\Development\Controls\Navigation\TreeView\Virtualization\IndexTree.cs:line 271 at Telerik.Windows.Controls.TreeView.TreeViewPanel.ExtendDesiredSize(ItemsControl itemsControl, Size stackDesiredSize, Int32 pivotIndex, Boolean before) in c:\TB\105\WPF_Scrum\Release_WPF\Sources\Development\Controls\Navigation\TreeView\Virtualization\TreeViewPanel.cs:line 2287 at Telerik.Windows.Controls.TreeView.TreeViewPanel.MeasureOverride(Size constraint) in c:\TB\105\WPF_Scrum\Release_WPF\Sources\Development\Controls\Navigation\TreeView\Virtualization\TreeViewPanel.cs:line 1680 === This item is declined because we are unable to reproduce such exception with our latest binaries.
Sometimes when using the treeview in TriStateMode I wish I could have the ability to uncheck all the children of an indeterminate parent with one click. Currently when a parent is in indeterminate mode and you click on it, it will activate it and all it's ================= Reason for Decline: This is a custom requriement and could be implemented as application logic based on this example: http://www.telerik.com/help/wpf/radtreeview-howto-tri-state-mvvm.html
Expand bottom up. ================= Reason for deletion: 0 votes for more than 4 years. Users can invoke in a loop ExpandItemByPath in order to achieve expanding from bottom to top.
The DefaultImageSrc property doesn't show the image when it is set to a relative file path. Reason for Decline: This is not actually a bug. When you set the DefaultImgSrc in XAML starting with "/" the Image is shown successfully. In WPF the relative image sources must begin with "/". http://msdn.microsoft.com/en-us/library/aa970069%28v=vs.110%29.aspx
A common request is to have a way to hide the root node of a RadTreeView so that the second-level nodes are displayed without a root. If the RadTreeView is bound, it appears that this can be done through the hierarchical binding if one know what one is doing. However, there does not seem to be a simple way to do it if the nodes to be added to the RadTreeView are added programmatically. It would be helpful if there were a binary property on the RadTeeView to set whether the root node is displayed. Reason for decline: Both in databound tree or not , you can add only the items you need to display in the root source / root items collection of the tree. Generally, there is no value of hiding a root node that has children - why is inside the collection at all ?
Change the selection on MouseLeftButtonUp instead of MouseLeftButtonDown. DECLINED: Duplicate with https://feedback.telerik.com/Project/143/Feedback/Details/112812-treeview-perform-selection-on-mouseleftbuttonup