http://blogs.msdn.com/b/oldnewthing/archive/2005/11/04/489028.aspx

Why is there a special PostQuitMessage function?

Because it's not really a posted message.

Commenter A. Skrobov asked, "What's the difference

between PostQuitMessage and PostThreadMessage (GetCurrentThreadId, WM_QUIT)?"

They are not equivalent, though they may look that way at first glance.

The differences are subtle but significant.

Like the WM_PAINTWM_MOUSEMOVE, and WM_TIMER messages,

the WM_QUIT message is not a "real" posted message.

Rather, it is one of those messages that the system generates as if it were posted, even though it wasn't.

And like the other messages, the WM_QUIT message is a "low priority" message,

generated only when the message queue is otherwise empty.

When a thread calls PostQuitMessage, a flag in the queue state is set that says,

"If somebody asks for a message and there are no posted messages, then manufacture a WM_QUIT message."

This is just like the other "virtually posted" messages.

WM_PAINT messages are generated on demand if there are any invalid regions,

WM_MOUSEMOVE messages are generated on demand if the mouse has moved since the last time you checked, and

WM_TIMER messages are generated on demand if there are any due timers.

And since the message is "virtually posted", multiple calls coalesce,

in the same way that multiple paint messages, multiple mouse motions, and multiple timer messages also coalesce.

Why is WM_QUIT handled like a low-priority message?

Because the system tries not to inject a WM_QUIT message at a "bad time";

instead it waits for things to "settle down" before generating the WM_QUIT message,

thereby reducing the chances that the program might be in the middle of a multi-step procedure triggered by a sequence of posted messages.

If you PeekMessage(..., PM_NOREMOVE) a WM_QUIT message, this returns a WM_QUIT message but does not clear the flag.

The WM_QUIT message virtually "stays in the queue". You can peek it use PeekMessage(..., PM_NOREMOVE) again ?

  i := ;
while TRUE do
begin
if LongInt( PeekMessage( Msg, , , , PM_REMOVE ) ) > then
begin
case Msg.message of
WM_QUIT :
begin
Inc( i );
if i = then           // First WM_QUIT posted by other thread
begin
for j := to do
PostQuitMessage( j );    // only 1 WM_QUIT in queue !
end else if i = then     // i = 2
break;              // Never be executed, unless other thread posted WM_QUIT again
end;
end;
end else begin
Sleep( );
end;
end;

Only can peek WM_QUIT once even if more WM_QUIT posted !

  i := ;
while TRUE do
begin
if LongInt( PeekMessage( Msg, , , , PM_REMOVE ) ) > then
begin
case Msg.message of
WM_QUIT :
begin
Inc( i );
if i = then         // First WM_QIUT from other thread       
begin
for j := to do
begin
PostQuitMessage( j );  // Only set "quit message pending" flag
PostThreadMessage( GetCurrentThreadId( ), WM_USER+j, , ); // 1024, 1025, ....
end;
end else if i = then  // Next WM_QUIT from this thread, but no more ...
break;
end;
else
begin
Sleep( );           // 1024, 1025, ...
end;
end;
end else begin
Sleep( );              //
end;
end;
  i := ;
while TRUE do
begin
if LongInt( PeekMessage( Msg, , , , PM_REMOVE ) ) > then
begin
case Msg.message of
WM_QUIT :
begin
Inc( i );
if i = then
begin
for j := to do
begin
PostThreadMessage( GetCurrentThreadId( ), WM_QUIT, , );    
PostThreadMessage( GetCurrentThreadId( ), WM_USER+j, , );   // WM_QUIT, WM_USER+0, WM_QUIT, WM_USER+1, ... 
end;
end else if i = then
break;
end;
else
begin
Sleep( );
end;
end;
end else begin
Sleep( );
end;
end; // Exit from here

As another special behavior, the generated WM_QUIT message

bypasses the message filters passed to the GetMessage and PeekMessage functions.

If the internal "quit message pending" flag is set, then you will get a WM_QUIT message once the queue goes quiet, regardless of what filter you pass.

By comparison, PostThreadMessage just places the message in the thread queue (for real, not virtually),

and therefore it does not get any of the special treatment that a real PostQuitMessage triggers.


PostQuitMessage : Set "quit message pending" flag, Generate a WM_QUIT when the queue goes quit

PostThreadMessage : Place WM_QUIT in queue


Thread0 : PostThreadMessage( ThreadId, WM_QUIT )

Thread1 : PostThreadMessage( ThreadId, WM_USER )

Thread2 : PostThreadMessage( ThreadId, WM_XXXX )

Thread3 : PostThreadMessage( ThreadId, WM_QUIT )

Thread4 : PostThreadMessage( ThreadId, WM_YYYY )

PeekMessage() : WM_USER, WM_XXXX, WM_YYYY, WM_QUIT

Because the system tries not to inject a WM_QUIT message at a "bad time";

instead it waits for things to "settle down" before generating the WM_QUIT message,

thereby reducing the chances that the program might be in the middle of a multi-step procedure triggered by a sequence of posted messages.

函数GetMessage里是使用一个循环不断地检测消息,周止复始的,是不可能出现死亡的,但它会检测到消息WM_QUIT就退出来。
 
那现在问题是谁发送WM_QUIT消息出来呢?这就是PostQuitMessage函数所做的工作。
 
当你点击窗口右上角的关闭时,Windows就会把窗口从系统里删除,这时就会发出消息WM_DESTROY给窗口消息处理函数WindowProc,
 
WindowProc收到这条消息后,最需要做的一件事情就是调用PostQuitMessage发出退出消息,让消息循环结束。
 
函数GetMessage检测到消息WM_QUIT就退出来。
 
函数PostQuitMessage声明如下:
 
WINUSERAPI
VOID
WINAPI
PostQuitMessage(
__in int nExitCode);

nExitCode是退出标识码,它被放到WM_QUIT消息的参数wParam里。

PostQuitMessage寄送一个WM_oUT消息给线程的消息队列并立即返回;

此函数向系统表明有个线程请求在随后的某一时间终止。

当线程从消息队列里取得WM_QUIT消息时,应当退出消息循环并将控制返回给系统。

返回给系统的退出值必须是消息WM_QUIT的wParam参数。

LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam)
{
int wmId, wmEvent;
PAINTSTRUCT ps;
HDC hdc; switch (message)
{
case WM_COMMAND:
wmId = LOWORD(wParam);
wmEvent = HIWORD(wParam); switch (wmId)
{
case IDM_ABOUT:
DialogBox(hInst, MAKEINTRESOURCE(IDD_ABOUTBOX), hWnd, About);
break;
case IDM_EXIT:
DestroyWindow(hWnd);
break;
default:
return DefWindowProc(hWnd, message, wParam, lParam);
}
break; case WM_PAINT:
hdc = BeginPaint(hWnd, &ps);
//
EndPaint(hWnd, &ps);
break; case WM_DESTROY:
PostQuitMessage(0);
break;
default:
return DefWindowProc(hWnd, message, wParam, lParam);
}
return ;
}

PostQuitMessage, PostThreadMessage( WM_QUIT )的更多相关文章

  1. WM_QUIT,WM_CLOSE,WM_DESTROY 消息出现顺序及调用方式

    http://bbs.ednchina.com/BLOG_ARTICLE_3005455.HTM VC中WM_CLOSE.WM_DESTROY.WM_QUIT消息出现顺序及调用方式 wxleasyla ...

  2. WM_CLOSE、WM_DESTROY、WM_QUIT的区别(询问,销毁窗口,退出进程,都不是一回事)

    1.发送消息SendMessage.PostMessage PostMessage将消息放入消息队列后马上返回,而SendMessage直到窗口过程处理完消息后才返回 2.三个消息的区别 WM_CLO ...

  3. Windows 消息机制详解

    总的来说: MSG包括: 窗口句柄,指示MSG发送的目的窗口 消息标识 lPARAM.wParam 发送时间 发送时的鼠标位置   关于消息队列: Windows系统有一个系统消息队列 每个线程都有一 ...

  4. 英文不好也能快速"记忆" API

    英文不好不要紧,把API函数导入打字练习类软件,即是练习打字速度,提高编程效率:也能短时间记忆API. 坚持每天打一遍,约2小时,连续打两周,会对API有很好的记忆,此方法是结合英文学习方法!以下是W ...

  5. Win32/MFC的基本概念

    一.MFC的基本概念 单文档.多文档和对话框框架的区别 MFC中的类继承图的基本框架 CView类与CDocument的关系 Onpaint()和Ondraw()的关系 hdc-cdc区别联系 RUN ...

  6. DMP文件的生成和使用

    1.生成dmp的程序 #include  <dbghelp.h> #pragma comment(lib,  "dbghelp.lib") //设置异常处理回调函数Se ...

  7. MFC OnOk(),OnCancel(),OnClose(),OnDestroy()的区别总结

    MFC OnOk(),OnCancel(),OnClose(),OnDestroy()的区别总结(转) 第一,OnOK()和OnCancel()是CDialog基类的成员函数,而OnClose()和O ...

  8. 第一个Windows窗口应用程序

    学习目的 熟悉开发工具Visual C++ 6.0和MSDN 2001的使用. 应用Windows API函数, 手工编写具有最基本构成的Windows窗口应用程序(包含WinMain入口函数, 消息 ...

  9. VC++SDK编程——模拟时钟

    #include <Windows.h> #include <tchar.h> #include <math.h> typedef struct Time { in ...

随机推荐

  1. shell脚本中一些特殊符号

    在shell中常用的特殊符号罗列如下: # ;   ;; . , / \\ 'string'| !   $   ${}   $? $$   $* \"string\"* **   ...

  2. C++ STL知识点小结

    1.capacity(容量)与size(长度)的区别. size(长度)指容器当前拥有的元素个数. capacity(容量)指容器在必须分配新存储空间之前可以存储的元素总数.

  3. 使用Junit实现批量运行

    我们知道使用testng可以很方便的实现批量运行,但有的同学更习惯用junit,那么junit是否也有批量运行的功能呢?答案是 YES,而且有2种方法: 第一种, 选择要测试的包(注意是包而不是文件) ...

  4. [python]使用pexpect模块进行批量scp

    #!/usr/bin/env python# -*- coding: utf-8 -*- #wangxiaofei #awcloud自动化测试 import time,osimport threadi ...

  5. Thrift框架介绍

    1.前言 Thrift是一个跨语言的服务部署框架,最初由Facebook于2007年开发,2008年进入Apache开源项目.Thrift通过一个中间语言(IDL, 接口定义语言)来定义RPC的接口和 ...

  6. iOS9对SDK的影响(iOS9适配必看)

      1.大部分社交平台接口不支持https协议. 问题描述:在iOS9下,系统默认会拦截对http协议接口的访问,因此无法获取http协议接口的数据.对ShareSDK来说,具体表现可能是,无法授权. ...

  7. freetds相关

    什么是FreeTDS  简单的说FreeTDS是一个程序库,可以实现在Linux系统下访问微软的SQL数据库! FreeTDS 是一个开源(如果你喜欢可以称为自由)的程序库,是TDS(表列数据流 )协 ...

  8. URAL-1998 The old Padawan 二分

    题目链接:http://acm.timus.ru/problem.aspx?space=1&num=1998 题意:有n个石头,每个石头有个重量,每个时间点你能让一个石头飞起来,但有m个时间点 ...

  9. WebRTC源码分析:音频模块结构分析

    一.概要介绍WebRTC的音频处理流程,见下图: webRTC将音频会话抽象为一个通道Channel,譬如A与B进行音频通话,则A需要建立一个Channel与B进行音频数据传输.上图中有三个Chann ...

  10. POJ 1410 Intersection(判断线段交和点在矩形内)

    Intersection Time Limit: 1000MS   Memory Limit: 10000K Total Submissions: 9996   Accepted: 2632 Desc ...