WM_TIMER<\/code> 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. <\/p>\n Why is WM_QUIT<\/code> handled like a low-priority message? <\/p>\n Because the system tries not to inject a WM_QUIT<\/code> message at a “bad time”; instead it waits for things to “settle down” before generating the WM_QUIT<\/code> 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. <\/p>\n If you PeekMessage(..., PM_NOREMOVE)<\/code> a WM_QUIT<\/code> message, this returns a WM_QUIT<\/code> message but does not clear the flag. The WM_QUIT<\/code> message virtually “stays in the queue”. <\/p>\n As another special behavior, the generated WM_QUIT<\/code> message bypasses the message filters passed to the GetMessage<\/code> and PeekMessage<\/code> functions. If the internal “quit message pending” flag is set, then you will get a WM_QUIT<\/code> message once the queue goes quiet, regardless of what filter you pass. <\/p>\n By comparison, PostThreadMessage<\/code> 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<\/code> triggers. <\/p>\n","protected":false},"excerpt":{"rendered":"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_PAINT, WM_MOUSEMOVE, and WM_TIMER messages, the WM_QUIT message […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-33453","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
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_PAINT, WM_MOUSEMOVE, and WM_TIMER messages, the WM_QUIT message […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/33453","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=33453"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/33453\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=33453"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=33453"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=33453"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}