Update: The latest version is currently only available through the download link below. And please leave your rating if you like the control 🙂 Nevertheless, I am going to present the very few and simple steps that I did to accomplish this daring and heroic feat :ġ – I pulled the TreeView control template with the Show Me The Template tool and copied it into my build directory to a new file named TreeViewForStrangeRequirement.xaml.Ģ – I then placed a TreeView in my window’s XAML and referenced this new template:ģ- I had a checkbox on my window which the user could check to show only the active tree view items or the user could uncheck it to show all active and inactive tree view items.Ĥ- I modified the control template at line 139 and added a MultiDataTrigger which triggered on this checkbox and on my view model’s IsActive property for each data item.A tutorial is now available on Code Project, so check the article for a detailed overview. Isn’t it strange that after you do something which had been challenging you and forcing you to struggle to surmount it, that it really doesn’t seem so difficult after you do it? I hate that feeling, it makes me feel like I didn’t do anything. It will be my project for the day and I can do this.” I felt the ‘force’ close by (well actually Josh Smith’s blog but close enough) and so I felt confident. So after I got over my rant, which took weeks, I took the time to sit down and tell myself “I am going to do this. I was thinking to myself, just how many templates are there any way? Do we actually need them? Come on Microsoft, make something easy for me for once. There is a control template, a data template, an items panel template, and others. As a matter of fact, I was quite confused by all of those ‘templates’ in WPF I kept hearing about and trying to read about. I am not a XAML expert and wanted no part with doing something like this.

In order to solve this problem and implement my requriement correctly, I knew I’d have to probably look at the TreeView’s control template and modify it. The default TreeView action when hiding an item was to hide that item’s children also regardless of if the children are active or not. But I soon realized that was not going to happen because although I was able to easily hide inactive tree view items, their children were hidden also. Walla! I was done and could move onto more pressing issues in the project. I was writing this project using the MVVM pattern and so in my first attempt at this requirement, I simply used some data triggers in my XAML to hide items which were marked inactive in my view model.

Software wpf treeview control template