RadTreeView with virtualization turned on, defines HierarchicalDataTemplates for its items. In the template, the root panel is 32 pixels (or higher than the default TreeViewItemHeight - 24 px in OfficeBlackTheme). Scrolling the treeview, then maximizing the wpf window results in misplaced / incorrect height of treeviewitems. Possible workaround: Set the MinHeight property of RadTreeViewItem so that all its header content fits. Then set the item's VerticalConentAlignment to Stretch <Style TargetType="telerik:RadTreeViewItem"> <Setter Property="MinHeight" Value="48" /> <Setter Property="VerticalContentAlignment" Value="Stretch" /> </Style> The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.
When the RadTreeViewItem (or the RadTreeView) is disabled and after a delay is enabled again it should go in "Normal" state. Now the control preserves its state, hence you are able to send more than one RadTreeViewItem in "Hovered" state.
If an item that has multiple parents is about to be edited, the PreviewEditStarted event handler is fired so many times as the number of the item's parents. In this case setting the e.Handled property to True doesn't work as expected. Will be available in R2 2016 Release.
Virtualized RadTreeView. Windows Display Size is set to Larger (150%). Expanding and collapsing TreeViewItems leads to ArgumentException in TreeViewPanel.ExtendDesiredSize method - "Width and Height must be non negative". Available in LIB version: 2015.3.1207
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 ?
RadTreeView or RadPanelBar has custom Style in which there is no ScrollViewer in the ControlTemplate. IsDragDropEnabled is set to true. When dragged item is dragged above the tree/panelbar - null reference exception occurs in RadTreeView.AutoScrolling.cs.
The CheckedItems collection is not cleared when ItemsSource is changed. Please consider CheckedItems as not supported collection in RadTreeView. In DataBinding scenarios , use the approach described in the following article: http://docs.telerik.com/devtools/wpf/controls/radtreeview/how-to/howto-tri-state-mvvm.html This way you will be able to create CheckedItems property in your ViewModels. The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.
When the TreeView's ScrollViewer is Visible, changing the tree's width to 0 them back to Auto breaks the scrolling function of the ScrollViewer. The workaround is to make the TreeView Collapsed before setting the Width to 0 and make it Visible before setting the Width back to Auto. Reason for declination: The feedback item is declined due to duplication with the one below: http://feedback.telerik.com/Project/143/Feedback/Details/113789-treeviews-scrolling-does-not-work-if-the-trees-width-is-set-to-0-and-then-back Please follow it instead.
When this property is set to false the changes are not saved. Edit: We have reviewed this item and we can confirm this is by design and it is not bug. IsInEditMode serves only for opening / closing the edit mode of the RadTreeViewItem. The way to submit changes is to use CommitEdit() method.
An appropriate ItemEditTemplate can be generated when the DisplayMemberPath property is used.
If the RadTreeView control is used on touch device in scenario with Checkbox support, the TreeViewItem cannot be (un)checked with a single tap. Available in LIB version: 2015.3.1109
When the data is bound to the RadTreeView the AutoScrollToSelectedItem doesn't work. The same behavior appears when the RadTreeViewItems are created declarative and the SelectedItem is set True on any of its root level items. Available in LIB version: 2014.3.1301
If you define a RadMaskedInput control in the ItemEditTemplate of RadTreeView and then bind the Value property of the masked input to a property from the RadTreeViewItem's view model, the input displays the view model's class ToString() method. Instead the value of the bound property should be displayed. Fix is available in LIB Version: 2015.3.1005.
Too many TreeViewItems are created internally when using virtualization. This causes the tree to consume large amount of space when performing virtualization intensive tasks like CollapseAll or ExpandAll. The XAML team recently reviewed this issue and will not be addressing it. On ExpandALL / CollapseALL virtualization creates / recycles / reuses containers - RadTreeViewItems. You cannot be sure when the GarbageCollector will free up the currently unused containers. Also after even number of invocations (ExpandAll + CollapseAll), the containers that are not freed up from memory is not increasing - it is constant which means there is no memory leak to worry for.
Implemented Multiple selection mode which is consistent with the same mode in RadListBox, RadGridView, etc. Multiple Selection refers to Selecting / Deselecting items with single Mouse click or single space key press. Until Q3 2015 this Extended ans Multiple Selection had the same behavior. Will be available in Q3 2015 Release.
RadTreeViewItem is focused but it is not selected. KeyDown should select the item below the focused one but it does not. Will be available in Q3 2015 Release.
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
TreeView is bound to CollectionViewSource. Certain items are expanded. The CVS is refreshed leading to ArgumentOutOfRange Exception in the TreeViewPanel.cs NOTE: The bug is reported via the following scenario. When the bound IsExpanded property is changed in the model, OnCollectionChanged with NotifyChangedCollectionAction.Reset is invoked. We consider this as highly unsafe operation. What actually happens is that by the time containers are measured / arranged (because the IsExpanded is triggered) - Reset also triggers reset / measure arrange of all items. This is the same as modifying a list/collection when it is iterated - the framework wll throw an error. To better prove this is unsafe, we also tested System.Windows.Controls.TreeView. On MouseDown, we set IsExpanded = true on collased item and in the PropertyChnaged handler we invoked OnCollectionChanged with Reset in the bound ObservableCollection. This resulted in StackOverflowException in PresentationCore.dll. Conclusions. The Exception is fixed in the RadTreeView but we consider invoking Reset in such moment (during measure/arrange) as not supported / critical / unsafe operation.
CheckState of the RadTreeViewItem is lost when a child item is added programmatically in the Items Collection. When the Items collection is just rechanged ( Items = new ObservableCollection<DataItem>) checkstate is NOT lost. Please use CheckBoxes in DataTemplates. The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.
When the ScrollViewer of a virtualized TreeView is visualized the bindings of the TreeViewItem are broken. We are closing this one because of duplication with the following item => http://feedback.telerik.com/Project/143/Feedback/Details/112754-treeview-bindingexpressionerror-occurs-in-situations-when-the-tree-is-virtualiz