arguments exactly. For example, ON_MESSAGE requires each handler to be
have any arguments. VC6 didn't enforce message handler signatures; VC2002+
Hi Joe,
Thank you for your response.
The issue is not recreatable, that is why I did not put a breakpoint there
and I do not know that actual values of the variables. I do not know the
purpose of the variables (m_nIDTracking and m_nIDLastMessage). Maybe I
shoud have studied the source code before posting the question...
What did you mean by "expression" ?
Thank you
Vaclav
Btw I am using VS6 if that makes a difference.
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:q33ss318o9htvk8lo4n2o64a2q6hdd02fi@4ax.com...
Would it not be apparent? Did you look at the values of nWhy and
m_nIDTracking?
Without telling us those values, all we can say is that the ASSERT is
detecting an error,
based on the criterion you gave in the expression. Perhaps your
expression is wrong? Or
perhaps your expression is correct and the ASSERT is indeed finding what
you asked it to
find...
joe
On Tue, 4 Mar 2008 23:20:48 +0100, "Vaclav" <vjedlicka@atlas.cz> wrote:
Hello,
Sometimes I get this assert in my MFC MDI app :
void CFrameWnd::OnEnterIdle(UINT nWhy, CWnd* pWho)
{
CWnd::OnEnterIdle(nWhy, pWho);
if (nWhy != MSGF_MENU || m_nIDTracking == m_nIDLastMessage)
return;
SetMessageText(m_nIDTracking);
ASSERT(m_nIDTracking == m_nIDLastMessage); <---here
}
Any idea?
Thanks
Vaclav
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm