DevBlog

Why can't someone build a tree view control with lots of features, an easy to use API, and a reasonable price? Come on, how hard can it be? For a project I'm working on, I've looked at about a dozen treeview controls...none of which have what I need. Yes, some come close, but are so complicated to use and with sparse documentation, that I can't figure out how to use them. I could handle a complicated interface if the docs explained how to use it. Here's what I need:

• Each item (node) must support a unique, user-defined key.
• A way to determine click, right-click, and double-click on each node.
• Multiple images. I don't mean one image for selected, one for open, one for closed, etc. What I want is a way to have the text, then an image to the right of the text. I need to change that image at anytime or even remove it completely. The image support has to be different for each node, not columnar where the image is defined for the entire column, then hidden/displayed on each node as needed.
• A simple interface to add, remove, and access each node.
• Affordable. Many treeviews come bundled with other controls and sell for $300 or more. I don't need all those other contols. Just the treeview.
• Must be ActiveX...not .NET.

If you have any ideas of a treeview that may meet my needs, let me know.

// posted by Craig Berntson @ 11:11:00 AM