Application Security Testing: An Integral Part of DevOps
Environment: VC6 SP2
The versions I have seen take the approach of handling the selection around the mouse-down, mouse-move and mouse-up messages, with variables holding state in-between. CMultiTree takes the approach of handling the whole multi-selection within the mouse-down handler. This is a closer approach to the underlying Windows treeview control.
CMultiTree attempts to mirror the selection behaviour of a CListCtrl (listview control) class. In fact the code was developed by putting a CListCtrl next to a CTreeCtrl and trying the combinations of mouse clicks/drags, and key presses. CMultiTree thus has full rubber-band selection support.
The sample application implements the CTreeCtrl in a CTreeView class, using a method described on a CodeGuru site. Unfortunately I can't find the original article to credit the author [hopefully the editor can do this on my behalf].
Multiple-selection in CMultiTree should be done in more or less the same way as in a CListCtrl, i.e. using SetItemState, GetItemState. I have taken the liberty of defining a TVIS_FOCUSED (the equivalent of LVIS_FOCUSED of the CListCtrl).
SetItemState / GetItemState:
These two methods have been over-scoped in the CMultiTree class to replace the underlying CTreeCtrl versions. Because they are NOT virtual, they must be called in the scope of the CMultiTree class (or derived class), otherwise they will not work, e.g.:
/* if m_tree is a CMultiTree */ CTreeCtrl *pTree = &m_tree; UINT nState = pTree->GetItemState(hItem, TVIS_FOCUSED|TVIS_SELECTED);
this will NOT call the CMultiTree version because of the non-virtual GetItemState.
Examine the header file for other methods, they are pretty self-explanatory.
Copyright (c) 1999 Richard Hazlewood.