Re: SetCheck

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Thu, 5 Jul 2007 22:09:42 -0700

Message-ID:

<5BC3D79B-E266-4E41-B305-198B03F84879@microsoft.com>

It happens to me when I use this form for changing the selection:

GetListCtrl().SetItemState(0, LVIS_SELECTED, LVIS_SELECTED | LVIS_FOCUSED);

My LVN_ITEMCHANGED handler gets called twice. I suspect this is because one
is losing focus and one is gaining focus.

Tom

"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:13ir83h289a99jgkp4m0ntub8tdmqj62f4@4ax.com...

ListBoxes certainly don't do this, and I can't recall ever having gotten a
notification
from a list control when I changed a selection programatically.

For the reasons I pointed out, Windows can't be changed; there are tens of
millions of
lines of code that only work correctly because they know the current
semantics. Whether
these make sense in the larger sense of design doesn't matter at this
point; the semantics
can't be changed. Look at the problems that rich edit has because users
expect to get
notifications of programmatic changes, and the lengthy SetEventMask
comment in EN_CHANGE
handlers is an indication of the problems of even this simple behavioral
discontinuity
joe