Developing a smarter approach to using CTreeCtrl

[Jesper Knudsen]

I am looking for strategies for using tree controls. The goal is to extend the CTreeCtrl (or maybe even build a new custom CWnd descendant tree control) in a way that makes it easy to use, and that hides away most of the uggly struct and message tweeking needed. At init I would want to add one single node, the root, to the tree control. And as user expands nodes, the tree would ask the node to list its children. For the tree to be able to ask nodes for children, we need some kind of "class ITreeNode" interface. Implementing this interface would enable an object to be represented as a node in the tree. And the object would itself be in charge of how it should be represented in the tree. The tree this way visualizes the object structure in memory, which is a fair approach imo. The treenode interface could look something like this... class ITreeNode { virtual CString GetTreeLabel() { return "Default"; } virtual void GetTreeChildren( CTreeNodeList& L ) {} virtual int GetTreeImage() { return 0; } virtual int GetTreeImageSelected( return GetTreeImage(); } } Did anyone experiment with anything like this?