Unplanned
Last Updated: 29 Dec 2016 16:01 by Shrinand
When placed in grid column with Auto width and had its own width set to Auto, the RadTreeView does not scroll.
Unplanned
Last Updated: 03 Jan 2017 21:09 by ADMIN
RadTreeView is virtualized and SelectionMode is set to "Extended". All ViewModels are selected and IsSelected of TreeViewitems is 2-way bound to IsSelected in the ViewModels. When clicking a TreeViewitem with Mouse, all other items are deselected. However, when scrolling we see that items are being prepared are not deselected - they are still selected.

This is due to a Limitation of the Virtualization mechanism - it does not know about the existance of the ViewModels and does not work with them. Virtualization works only with the Containers - the RadTreeViewItem.
Completed
Last Updated: 29 Dec 2016 15:58 by ADMIN
SelectedItems collection does not work correctly when the RadTreeView is virtualized and ContainerBindings (SL) / Style Bindings (WPF) are used for binding the IsSelected property.


The issue is not reproducible with R3 2016 version of RadTreeView with both Multiple and Extended Selection mode.
Please open a new support thread with detals from your scenario if you encounter similar issue.
Declined
Last Updated: 11 Aug 2016 14:04 by ADMIN
Items are lost after reexpanding when TreeView is Virutalized and items are set in XAML.
Currently the TreeView does not support virtualization when using XAML items.

Reason for Decline: Virtualization is not supported in non-databound treeviews.
Unplanned
Last Updated: 27 Dec 2016 11:41 by ADMIN
BindingExpressionError occurs in situations  when the tree is virtualized and TemplateSelectors are used
Declined
Last Updated: 11 Aug 2016 14:04 by ADMIN
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.
Won't Fix
Last Updated: 21 Jul 2015 11:23 by ADMIN
TreeView: When the header of an Item is set to a TextBox, the selection of a RadTreeViewItem is incorrect

The original reported issue is that the following style does not work as expected.
<Style TargetType="telerik:RadTreeViewItem">
<Style.Triggers>
<Trigger Property="IsKeyboardFocusWithin" Value="True">
<Setter Property="IsSelected" Value="True" />
<Setter Property="Tag" Value="Selected" />
</Trigger>
<Trigger Property="IsKeyboardFocusWithin" Value="False">
<Setter Property="IsSelected" Value="False" />
<Setter Property="Tag" Value="Unselected" />
</Trigger>
</Style.Triggers>
</Style>

This is not supported by the RadTreeView Selection logic. Once the trigger applies with Selected / True, the IsSelected property is Locally set via the selector's code. This means future work of the trigger will not be successful over the IsSelected Property.
==================
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.

Unplanned
Last Updated: 03 Jan 2017 21:17 by ADMIN
Change the SelectedValue implementation to allow a TwoWay binding
Unplanned
Last Updated: 25 Nov 2016 16:38 by ADMIN
Root level items ItemTemplate is incorrectly set after virtualization when using HierarchicalDataTemplate with ItemTemplateSelector.
This causes the second level items to use incorrect data template.
Unplanned
Last Updated: 27 Dec 2016 12:46 by ADMIN
RadTreeView and RadTreeViewItem ExpandAll() method sets the IsExpanded property to True to all items even if an Item has no children to display. This causes an issue when using the DefaultImageSrc and ExpandedImageSrc properties as the last-level items will be displayed with an ExpandedImageSrc as their IsExpanded property it set to True. However, as these items have no children, they should use the DefaultImageSrc.
Won't Fix
Last Updated: 22 Jul 2015 13:31 by Eisa Baker
Tree is Virtualized and bind to colelction of DataItems.
On a button click, we add new Dataitem with IsInEditMode = true (bound to IsInEditMode of the RadTreeViewItem).
The new Item is in edit mode but the textBox in the ItemEditTemplate has no DataContext so no actual editing  can be performed.

Scenario casn be solved with adding the item, then switch its editmode in dispatcher:
DataItem item = new DataItem() { Name = "Item Editable" };
             
            (this.tree.ItemsSource as ObservableCollection<DataItem>).Insert(0, item);

            Dispatcher.BeginInvoke(new Action(() =>
            {
                item.IsInEditMode = true;
            }), DispatcherPriority.Loaded);

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.

Unplanned
Last Updated: 19 Mar 2019 15:39 by ADMIN
Currently, in Extended SelectionMode,  RadTreeView selects multiple Items with Shift + Click selection only if there is another RadTreeViewItem already selected with mouse.

Other controls like RadListBox, RadGridView hold reference to the business object which should be the start (the target) of the multiselection. RadTreeView holds such reference with weak reference to the container (RadTreeViewItem) and only if this container is selected with Mouse.

Adding such method (SetSelectionAnchor) in RadTreeView will help users better control the multiselection process.
Declined
Last Updated: 17 Jan 2020 09:16 by ADMIN

When a large number of items are selected through extended selection (with a lot of items on the first level of the RadTreeView) the selection does not work correctly. 

Workaround - make the selection in viewmodels manually and provide 2way bindings in style
 <telerik:RadTreeView.ItemContainerStyle>
                <Style TargetType="telerik:RadTreeViewItem">
                    <Setter Property="IsSelected" Value="{Binding IsSelected, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged}" />
                    <Setter Property="IsExpanded" Value="{Binding IsExpanded, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged}" />
                </Style>
            </telerik:RadTreeView.ItemContainerStyle>
private void SomeRadTreeView_SelectionChanged(object sender, SelectionChangedEventArgs e)
        {
            int count = e.AddedItems.Count;
            if (count > 1)
            {
                SomeViewModel first = e.AddedItems[0] as SomeViewModel;
                SomeViewModel last = e.AddedItems[count - 1] as SomeViewModel;
                
                this.SomeRadTreeView.SelectionChanged -= this.SomeRadTreeView_SelectionChanged;
                this.SomeRadTreeView.AutoScrollToSelectedItem = false;
                this.ViewModel.SelectRange(first, last);
                this.SomeRadTreeView.AutoScrollToSelectedItem = true;
                this.SomeRadTreeView.SelectionChanged += this.SomeRadTreeView_SelectionChanged;
            }
        }

Won't Fix
Last Updated: 22 Jul 2015 13:38 by Corey
ADMIN
Created by: Petar Mladenov
Comments: 1
Category: TreeView
Type: Bug Report
5
When a checked item is loading on demand its check state is lost.
This issue is applicable for both WPF and Silverlight.
And the issue is present always (no matter if the RadTreeView is databound, virtualized, etc).

Edit: Please use the approach from this help article if you need checkboxes in the RadTreeView.
http://docs.telerik.com/devtools/wpf/controls/radtreeview/how-to/howto-tri-state-mvvm.html

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.

Won't Fix
Last Updated: 20 Jul 2015 15:14 by ADMIN
When TreeView is databound to RadObservableCollection and Suspen/Resume Notifications are used when removing items the Selected items collection contains empty object at the end after deleting item and selecting another one.

As a workaround you can use ObservableCollection.


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.
Unplanned
Last Updated: 29 Dec 2016 14:39 by ADMIN
The TreeViewItems are expanded and collapsed on MouseLeftButtonUp which leads to an expand/collapse operation even if the MouseLeftButtonDown event was fired by another element. This can be easility reproduced if you hold down the mouse left button over any element outside the RadTreeView and then releasing it over any RadTreeViewItem when the RadTreeView IsExpandOnSingleClickEnabled is True.

It can also be reprorduced with the following steps:
1) left click on a node and hold the mouse button down
2) release the mouse when over a non-selected node that has children.
The result is expanding/collapsing the unselected node.
Declined
Last Updated: 03 Sep 2014 11:19 by ADMIN
The TreeView should be able to figure out the Old / NewValue for its event args during editing.
====
======

Reason for deletion. In databound scenarios e.OldValue and e.NewValue refer to the same instance of the ViewModel which is expected. 

Saving the state of the ViewModels means creating an entire deep copy of the ViewModel. We believe there is no such control in the framework to save the states of its ViewModels during editing.

We have to admin, introducing public properties OldValue and NewValue of type objects for these event args is a bad design. This is a bug since these are public but we won't fix it due to the complexity (described above).
Completed
Last Updated: 04 Nov 2014 09:11 by ADMIN
ADMIN
Created by: Telerik Admin
Comments: 0
Category: TreeView
Type: Bug Report
4
It should be possible to collapse certain items to filter them out. This should not affect the look or functionality of the 

This is already implemented => you can use the ItemVisibility property of the RadTreeView.
Won't Fix
Last Updated: 21 Jul 2015 11:28 by Miroslav Paskov
There should be a way to exclude the partially checked items from the CheckedItems collection. 
A a property can be added to specify whether they will be included.

Edit: Please avoid using this collection because it ihas never been implemented completely in the RadTreeView. In DataBinding scenarios, you can use CheckBox in the ItemTemplate of the RadTreeView. Approach can be found here =>
http://docs.telerik.com/devtools/wpf/controls/radtreeview/how-to/howto-tri-state-mvvm.html 
CheckedItems colelction can be implemented in the ViewModels, instead of using the built-in property.

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.
Won't Fix
Last Updated: 29 Dec 2016 14:37 by ADMIN
ADMIN
Created by: Telerik Admin
Comments: 0
Category: TreeView
Type: Bug Report
4
This issue is applicable to Silverlight ONLY!

We have a RadTreeView with following properties IsLoadOnDemandEnabled="True", IsVirtualizing="True" and SelectionMode="Extended" set.
We select an element, collapse his parent and select another item. At this point if we expand the previously parent, both the newly selected item and the the first selected item are selected.
It is not correct the first item to preserve its selection state.

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.