CListCtrl arrow key navigation

[dennisV]

Hello, Please help me with CListCtrl arrow key navigation - I have my own listctrl class, but when I use the arrow keys to scroll up and down though it, the current item is not identified correctly (I use UINT whichItem=GetNextItem(-1,LVNI_SELECTED)). It is updated one step behind, i.e. I'm on item 0, I press the down arrow, the whichItem is still 0, I press the down arrow again and then it becomes 1. Maybe I need to implement a keyboard handler in my derived class or something? :confused: Thanks in advance, Dennis MCP, MCSD

[Shog9 0]

Where are you trying to retrieve the current item? If it's from a state-changing notification, then the previous item may yet be selected.

---

Shog9 If I could sleep forever, I could forget about everything...

[dennisV]

I'm trying to get this in the OnLvnKeydown by responding to this: ON_NOTIFY(LVN_KEYDOWN, IDC_LIST, OnLvnKeydown) (and in my previous code I of course meant cList.GetNextItem(), instead of GetNextItem() - I'm not trying to get this from inside my derived class). MCP, MCSD

[Shog9 0]

Ok, that makes sense now. Unless you specifically need to pay mind to keyboard selection while excluding all other forms, it would be easier for you to use the notification LVN_ITEMCHANGED and watch for changes to the selection state:

void CMyWin::OnItemchangedListCtrl(NMHDR* pNMHDR, LRESULT* pResult)
{
NMLISTVIEW* pNMListView = (NM_LISTVIEW*)pNMHDR;
*pResult = 0;
if ( pNMListView->iItem < 0 )
return;

if ( (pNMListView->uOldState & LVIS_SELECTED)
&& !(pNMListView->uNewState & LVIS_SELECTED) )
{
// item has lost selection
}
else if ( !(pNMListView->uOldState & LVIS_SELECTED)
&& (pNMListView->uNewState & LVIS_SELECTED) )
{
// item has gained selection
}
}

---

Shog9 If I could sleep forever, I could forget about everything...

[dennisV]

Yeah, that code works, thanks. I was watching for the OnItemChanged in another list I had, but that was to process checkmarks, for some reason I didn't think about watching for selection as well. :(( Could've saved me some time :cool: But I really don't understand why it doesn't process the OnKeyDown correctly. MCP, MCSD

[Shog9 0]

dennisV wrote: But I really don't understand why it doesn't process the OnKeyDown correctly. Most likely it sends the notification *before* it does it's own processing, thus the selection doesn't get changed until after your notification handler returns. Couldn't say why they did it that way, but you're usually better off not using it for selection changes anyway, as it'll ignore the mouse.

---

Shog9 If I could sleep forever, I could forget about everything...