VS2010 MFC的小Bug-ASSERT(ContinueModal());

CWnd::RunModalLoop

		do
		{
			ASSERT(ContinueModal());

			// pump message, but quit on WM_QUIT
			if (!AfxPumpMessage())
			{
				AfxPostQuitMessage(0);
				return -1;
			}

			// show the window when certain special messages rec'd
			if (bShowIdle &&
				(pMsg->message == 0x118 || pMsg->message == WM_SYSKEYDOWN))
			{
				ShowWindow(SW_SHOWNORMAL);
				UpdateWindow();
				bShowIdle = FALSE;
			}

			if (!ContinueModal())
				goto ExitModal;

			// reset "no idle" state after pumping "normal" message
			if (AfxIsIdleMessage(pMsg))
			{
				bIdle = TRUE;
				lIdleCount = 0;
			}

		} while (::PeekMessage(pMsg, NULL, NULL, NULL, PM_NOREMOVE));
	}

在以上代码中

ASSERT(ContinueModal());

这个会判断 m_nFlags 的值来断言, 如果没有没有 WF_CONTINUEMODAL 属性将会报告异常, 但是循环有 PeekMessage

PeekMessage会进入内核的消息引擎会处理其他线程发送的消息

如果其他线程这时有 SendMessage(WM_CloseDlg); 而且据这个消息用 OnOK  EndModalLoop之类的关闭了对话框, 就会修改m_nFlags 的值

这时就会出现断言, ASSERT(ContinueModal());

要避免这个问题把 SendMessage(WM_CloseDlg);  修改为 PostMessage, 让循环的 AfxPumpMessage 来处理消息, 避免 PeekMessage 来处理