SetMessageQueue Used in MFC WinMain

ID: Q118611

The information in this article applies to:

The Microsoft Foundation Classes (MFC), included with:
- Microsoft Visual C++ for Windows, 16-bit edition, versions 1.5, 1.51, 1.52
- Microsoft Visual C++, 32-bit Editions, versions 2.0, 2.1

SUMMARY

Functions that use the applications message queue do not work correctly if they are called in the constructor of a global or static object. SetMessageQueue is called in the initialization code at the beginning of the MFC WinMain() function. SetMessageQueue replaces the current message queue with a new message queue. The constructors of global or static C++ objects are called before WinMain(). If these constructors call functions that rely on the message queue, the objects do not work properly.

MORE INFORMATION

MFC for Windows, version 2.5, calls SetMessageQueue in the AfxWinInit() function, which is called by the MFC WinMain() function. The constructors for global and static objects are called before WinMain(). These constructors should not call functions that use the applications message queue or rely on the message queue remaining the same after the constructor is executed. These functions include:

Creating a window

Setting a timer (using SetTimer)

Setting a hook (using SetWindowsHook)

Posting a message

If any one of these things is done in the constructor and is not processed or removed from the application's message queue before the constructor exits, it will not work later in the application. To work around this, initialize each of these objects in the CWinApp::InitInstance() function: Define an initialization member function for the object and call it in the CWinApp::InitInstance() function.

Additional query words: kbinf 1.50 2.00 2.10 2.50 2.51 2.52 3.00 3.10


Keywords          : kbnokeyword kbMFC kbVC 
Version           : 1.50 1.51 1.52 | 2.00 2.10
Platform          : NT WINDOWS 
Issue type        :

Last Reviewed: July 27, 1999