On Sat, 2005-05-14 at 11:12 -0500, James Hawkins wrote:
- LVHITTESTINFO lvHitTestInfo;
- INT nItem;
- if (infoPtr->bLButtonDown) {
lvHitTestInfo.pt = infoPtr->ptClickPos;
nItem = LISTVIEW_HitTest(infoPtr, &lvHitTestInfo, TRUE, TRUE);
if (LISTVIEW_TrackMouse(infoPtr, infoPtr->ptClickPos)) {
NMLISTVIEW nmlv;
ZeroMemory(&nmlv, sizeof(nmlv));
nmlv.iItem = nItem;
nmlv.ptAction.x = infoPtr->ptClickPos.x;
nmlv.ptAction.y = infoPtr->ptClickPos.y;
notify_listview(infoPtr, LVN_BEGINDRAG, &nmlv);
return 0;
- }
Please use 4-space indentation for new code.
Currently listview is a mixture of 2/4 space indentation, but we should be moving towards 4 spaces if it's not a problem.
On 5/14/05, Dimi Paun dimi@lattica.com wrote:
On Sat, 2005-05-14 at 11:12 -0500, James Hawkins wrote:
- LVHITTESTINFO lvHitTestInfo;
- INT nItem;
- if (infoPtr->bLButtonDown) {
lvHitTestInfo.pt = infoPtr->ptClickPos;
nItem = LISTVIEW_HitTest(infoPtr, &lvHitTestInfo, TRUE, TRUE);
if (LISTVIEW_TrackMouse(infoPtr, infoPtr->ptClickPos)) {
NMLISTVIEW nmlv;
ZeroMemory(&nmlv, sizeof(nmlv));
nmlv.iItem = nItem;
nmlv.ptAction.x = infoPtr->ptClickPos.x;
nmlv.ptAction.y = infoPtr->ptClickPos.y;
notify_listview(infoPtr, LVN_BEGINDRAG, &nmlv);
return 0;
- }
Please use 4-space indentation for new code.
Currently listview is a mixture of 2/4 space indentation, but we should be moving towards 4 spaces if it's not a problem.
K sounds good. I usually do 4 space tabs, but I tried to keep with the style around the area being changed, but I can change it to 4 space tabs.