I'm a relatively newcomer to the rather complex world of
building applications with Microsoft's MFC, and I'd like to
thank M. Lantsman for the Multi-column tree control. I've
been studying and modifying parts of it, but there are some
questions for which I haven't found any answers yet. So,
I'm turning to you and your experience with the hope you might give me some pieces of advice. Here are the
- Is it possible to edit the content ("label") of the
columns in the tree ?
I've tried some things, like using the Set_Editable option
in the Create call for the tree, but nothing happens upon
- How come the application crashes when calling New File or
Open File ?
The crash comes in upon the call to SubclassDlgItem in the
OnInitialUpdate function of CTreeListView.
It's a if some element should have been deleted before the
new document is created, but wasn't...
Thanks in advance,
Computer Sciences Student
Computer Vision and Systems Laboratory
Universit� Laval, Qu�bec, Canada
I've implemented this control in my MFC app and it works fine, but I'd also like to implement flicker free drawing - as all the other controls in my app have. I have consulted the <a href=http://codeguru.earthweb.com/controls/flicker_free_3.shtml>;article on the CMemDC class</a> by Thomas Jansen but so far my attempts to implement CMemDC have been unsuccessful; when resizing the view the control still flickers.
Has anyone successfully implemented flickerfree drawing for the CNewTreeListCtrl? How is it done? Thanks in advance.
First of all: great control - as far as I know, it's the best treelist ctrl available on the net.
I was just a little annoyed by the 'double' sunken border that appeared when using the CNewTreeListCtrl in a CFormView-derived class. The solution was to remove the WS_BORDER style from the (empty) dialog used as the CFormView's template dlg; so instead, use an empty dlg with no WS_BORDER or WS_EX_CLIENTEDGE etc.
The InsertItem and SetSubstring class both take a
CString by value. Changing these calls to take
LPCTSTR's may be a viable option.
The effect is a CString is copied or constructed on the
way in to either function (which when InsertItem is
being called the string first gets constructed and then
when it calls SetSubstring is constructs yet another
copy of that CString).