I've got a listview in which I when the "up" or "down" arrow is pressed when on the top or bottom rows the contents of the listview are reloaded and I set the bottom / top row as focussed and selected.
The problem is that the actual focussed and selected row becomes the second one / one before last. I take it that that happens because the listviews internal mechanics still see the "up" / "down" keypress and executes it - after I placed the "cursor" on the top / bottom row.
My question therefore is:
Can I, in the LVN_KEYDOWN event, either erase the keystroke or mark the it
as already having been handled ?
Why use LVN_KEYDOWN instead of LVN_ITEMCHANGED?
No. Because WM_NOTIFY is just a notice of something which has
already occured and processed.
And I can't believe I did not think of trying to use the LVN_KEYUP notification until now. The only problem is that that notification doesn't exist .... :-( :-)
|Location:||Huddersfield, West Yorkshire, UK|
|Nodes:||16 (1 / 15)|