Hi
First post here. Have really loved the trial of the Silverlight Controls, so bought the product.
I'm mainly using the Silverlight Treeview at the moment, the choice being made because of the virtualisation which the Silverlight Toolkit version didn't offer. I have a tree with ~130000 nodes, being semi built on demand, such that the first few levels are loaded straight away and then when a node is expanded, I fetch its grand-children, having already got its children. It means that the user experience is reasonably good.
One thing I do need to do with that volume of nodes is to prevent the user from Expanding All nodes, by pressing * on the numeric keypad or whatever other methods there are and this is particularly vital when at the top of the tree. Further down, I can live with, but an all or nothing approach is fine.
What's the best way of achieving this? I am using an MVVM approach, so am guessing an attached behaviour of some kind is needed?
Many thanks
Graham
First post here. Have really loved the trial of the Silverlight Controls, so bought the product.
I'm mainly using the Silverlight Treeview at the moment, the choice being made because of the virtualisation which the Silverlight Toolkit version didn't offer. I have a tree with ~130000 nodes, being semi built on demand, such that the first few levels are loaded straight away and then when a node is expanded, I fetch its grand-children, having already got its children. It means that the user experience is reasonably good.
One thing I do need to do with that volume of nodes is to prevent the user from Expanding All nodes, by pressing * on the numeric keypad or whatever other methods there are and this is particularly vital when at the top of the tree. Further down, I can live with, but an all or nothing approach is fine.
What's the best way of achieving this? I am using an MVVM approach, so am guessing an attached behaviour of some kind is needed?
Many thanks
Graham