In the handler I do an AfxMessgeBox and print the current selection.
First time it's the previous selection. The second it's -1(no
selection) and finally the third it's the new selection. I've found a
way to get around two extra (useless) calls but can't escape the
feeling that I'm doing something wrong. It seems too silly for this to
be a behaviour by design.
Any comments?!
--
Alex.
gu...@cyberdude.com
This is by design:
The first notification says that the previous item has been deselected
The second notification says that the new item has been selected
Not sure why you get three though, although it may be notification of
focus change.
You should examine the NMLISTVIEW structure to find out what has
changed, and only change the selection if the LVIS_SELECTED bit has
been set.
Tony
-----------------------------------------------------------------------------
Home: (+44) 161 737 0008 Work: (+44) 161 278 2463
Email:t...@netfusion.co.uk <><
ICQ: 13746312
Homepage: http://sale.netfusion.co.uk (Last update 24/6/98)
-----------------------------------------------------------------------------
--
Alex.
--