we\'re trying to come up with a good way to virtualize the TreeView
, the data is not really a problem because it\'s very light (around 16 bytes per item), the probl
We are also in a similar situation, we tried using Syncfusion tree-view and it was pathetic. As we didn't had the choice of any other 3'rd party control and no better solution was available, We finally settled with Virtualization and Load on demand(Lazy loading) together.
As in our case, generally all nodes won't be expanded at any given time. This solves the scrolling issues to some extent and makes the application usable in most of the scenarios. Although we still have our figures crossed and keep looking for a better solution.
I would like to mention here that using both Virtualization and Load on demand(Lazy loading) together have its own side effects -
Need a sample for WPF TreeView search with Virtualization and Load On Demand
.
Some samples for implementing Load on demand -
http://www.codeproject.com/KB/WPF/WPF_Explorer_Tree.aspx
http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/1eb3ed3d-6379-4353-9f35-2c0aecb885f2/
http://www.telerik.com/help/wpf/radtreeview-features-load-on-demand.html