I have a hypothetical tree view that contains this data:
RootNode
Leaf
vein
SecondRoot
seeds
flowers
I am trying to filter the nodes in order to show only the nodes that contain a certain text. Say if I specify "L", the tree will be filtered and show only RootNode->Leaf and SecondRoot->flowers (because they both contain the letter L).
Following the m-v-vm pattern, I have a basic TreeViewViewModel class like this:
public class ToolboxViewModel
{
...
readonly ObservableCollection<TreeViewItemViewModel> _treeViewItems = new ObservableCollection<TreeViewItemViewModel>();
public ObservableCollection<TreeViewItemViewModel> Headers
{
get { return _treeViewItems; }
}
private string _filterText;
public string FilterText
{
get { return _filterText; }
set
{
if (value == _filterText)
return;
_filterText = value;
ICollectionView view = CollectionViewSource.GetDefaultView(Headers);
view.Filter = obj => ((TreeViewItemViewModel)obj).ShowNode(_filterText);
}
}
...
}
And a basic TreeViewItemViewModel:
public class ToolboxItemViewModel
{
...
public string Name { get; private set; }
public ObservableCollection<TreeViewItemViewModel> Children { get; private set; }
public bool ShowNode(string filterText)
{
... return true if filterText is contained in Name or has children that contain filterText ...
}
...
}
Everything is setup in the xaml so I see the treeview and search box.
When this code is exercised, the filter only applies to the Root nodes which is insufficient. Is there a way to make the filter trickle down in the hierarchy of nodes so that my predicate is called for every node ? In other words, can the filter be applied to the TreeView as a whole ?
This is how I filtered the items on my TreeView
:
I have the class:
class Node
{
public string Name { get; set; }
public List<Node> Children { get; set; }
// this is the magic method!
public Node Search(Func<Node, bool> predicate)
{
// if node is a leaf
if(this.Children == null || this.Children.Count == 0)
{
if (predicate(this))
return this;
else
return null;
}
else // Otherwise if node is not a leaf
{
var results = Children
.Select(i => i.Search(predicate))
.Where(i => i != null).ToList();
if (results.Any()){
var result = (Node)MemberwiseClone();
result.Items = results;
return result;
}
return null;
}
}
}
Then I could filter results as:
// initialize Node root
// pretend root has some children and those children have more children
// then filter the results as:
var newRootNode = root.Search(x=>x.Name == "Foo");
Unfortunately there is no way to make same Filter apply to all nodes automatically. Filter is a property (not a DP) of ItemsCollection which is not DependencyObject and so DP Value inheritance isn't there.
Each node in the tree has its own ItemsCollection which has its own Filter. The only way to make it work is to manually set them all to call the same delegate.
Simplest way would be to expose Filter property of type Predicate<object> at your ToolBoxViewModel and in its setter fire an event. Then ToolboxItemViewModel will be responsible for consuming this event and updating its Filter.
Aint pretty and I'm not sure what the performance would be like for large amounts of items in the tree.
The only way I've found to do this (which is a bit of a hack), is to create a ValueConverter that converts from IList to IEnumerable. in ConvertTo(), return a new CollectionViewSource from the passed in IList.
If there's a better way to do it, I'd love to hear it. This seems to work, though.
Why do you need filters or CollectionSource? Here is a simple MVVM way to handle TreeView items.
You can make items visible, collapsed, change color, highlight, flash, whatever, simply by using DataTriggers:
public class Item : INotifyPropertyChanged
{
public string Title { get; set; } // TODO: Notify on change
public bool VisibleSelf { get; set; } // TODO: Notify on change
public bool VisibleChildOrSelf { get; set; } // TODO: Notify on change
public ObservableCollection<Item> Items { get; set; } // TODO: Notify on change
public void CheckVisibility(string searchText)
{
VisibleSelf = // Title contains SearchText. You may use RegEx with wildcards
VisibleChildOrSelf = VisibleSelf;
foreach (var child in Items)
{
child.CheckVisibility(searchText);
VisibleChildOrSelf |= child.VisibleChildOrSelf;
}
}
}
public class ViewModel : INotifyPropertyChanged
{
public ObservableCollection<Item> Source { get; set; } // TODO: Notify on change
public string SearchText { get; set; } // TODO: Notify on change
private void OnSearchTextChanged() // TODO: Action should be delayed by 500 millisec
{
foreach (var item in Source) item.CheckVisibility(SearchText);
}
}
<StackPanel>
<TextBox Text="{Binding SearchText, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged}"
MinWidth="200" Margin="5"/>
<TreeView ItemsSource="{Binding Source}" Margin="5">
<TreeView.ItemTemplate>
<HierarchicalDataTemplate ItemsSource="{Binding Items}">
<TextBlock Text="{Binding Title}" />
</HierarchicalDataTemplate>
</TreeView.ItemTemplate>
<TreeView.ItemContainerStyle>
<Style TargetType="Control">
<Style.Triggers>
<DataTrigger Binding="{Binding VisibleChildOrSelf}" Value="false">
<Setter Property="Visibility" Value="Collapsed"/>
</DataTrigger>
<DataTrigger Binding="{Binding VisibleSelf}" Value="false">
<Setter Property="Foreground" Value="Gray"/>
</DataTrigger>
</Style.Triggers>
</Style>
</TreeView.ItemContainerStyle>
</TreeView>
<StackPanel>
I'm going to include the complete example into my WPF library:
https://www.codeproject.com/Articles/264955/WPF-MichaelAgroskin
I decided to use the treeview by Philipp Sumi mentioned here : http://www.codeproject.com/KB/WPF/versatile_treeview.aspx
And applied a filter to it as shown here : http://www.hardcodet.net/2008/02/programmatically-filtering-the-wpf-treeview
I couldn't recommend it enough :)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With