C / C++ / MFC

sawerr wrote:

We know that Windows keeps a message queue for every thread.

sawerr wrote:

for win32 applications, only one message loop is enough.

sawerr wrote:

Do all of the message map macros that we see in the source code indicate there is a message loop that buried in MFC source code?

Mark Salsbery
Microsoft MVP - Visual C++

hEdit = CreateWindowEx(WS_EX_CLIENTEDGE, "EDIT", "", 
            WS_CHILD | WS_VISIBLE | WS_VSCROLL | WS_HSCROLL | ES_MULTILINE | ES_AUTOVSCROLL | ES_AUTOHSCROLL, 
            0, 0, 100, 100, hwnd, (HMENU)IDC_MAIN_EDIT, GetModuleHandle(NULL), NULL);
//<a href="http://www.winprog.org/tutorial/app_one.html">http://www.winprog.org/tutorial/app_one.html</a>[<a href="http://www.winprog.org/tutorial/app_one.html" target="_blank" title="New Window">^</a>]

//class CTextView : public CEditView

void CTextView::OnClose()
{
	// TODO: Add your message handler code here and/or call default

	CEditView::OnClose();
}

Mark Salsbery wrote:

The CWinApp class derives from CWinThread, so for an MFC GUI app,
your required CWinApp object generally provides the first/main
message loop

sawerr wrote:

Here we create a "control". That control has a message loop in its source code which was written by controls developer.

sawerr wrote:

If view window has a message loop, is that mean it is created by a new thread?

Mark Salsbery
Microsoft MVP - Visual C++

Mark Salsbery wrote:

You're confusing message loops with window procedures.

followait wrote:

BTW, it may be easy for UNIX, coz everything in UNIX is a file.