Message loop in Microsoft Windows

Microsoft Windows programs are event-based. They act upon messages that the operating system posts to the main thread of the application. These messages are received from the message queue by the application by repeatedly calling the GetMessage (or PeekMessage) function in a section of code called the "event loop." The event loop typically appears as follows:

 int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
 {
   MSG msg;
   while(GetMessage(&msg, NULL, 0, 0) > 0)
   {
     TranslateMessage(&msg);
     DispatchMessage(&msg);
   }
   return msg.wParam;
 }

Though not strictly required, it's conventional for the event loop to call TranslateMessage and DispatchMessage, which transfers the message to the callback procedure associated with the window the message refers to.

Modern graphical interface frameworks, such as WinForms, Windows Presentation Foundation, MFC, Delphi, Qt et al. do not typically require applications to directly access the Windows message loop, but instead automatically route events such as key presses and mouse clicks to their appropriate handlers as defined within the framework. Underlying these frameworks, however, the message loop can again be found, and can typically be accessed when more direct control is required.

External links

• Meandering Through the Maze of MFC Message and Command Routing
• A Key's Odyssey: the path of a keystroke message through the VCL
• Platform SDK: Message and Message Queue Overviews
• Platform SDK: Windows API: Entering the Message Loop
• GetMessage function
• PeekMessage function