{"id":112082,"date":"2026-02-24T07:00:00","date_gmt":"2026-02-24T15:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=112082"},"modified":"2026-02-24T07:01:30","modified_gmt":"2026-02-24T15:01:30","slug":"20260224-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20260224-00\/?p=112082","title":{"rendered":"Customizing the ways the dialog manager dismisses itself: Isolating the Close pathway"},"content":{"rendered":"

We started by exploring the signals the dialog manager uses for dismissing a dialog<\/a>. Now we can use that information to customize the dismiss behavior.<\/p>\n

Let’s start with a diagram, because people like diagrams.<\/p>\n\n\n\n\n\n\n\n
 <\/td>\n <\/td>\nWM_SYS\u00adCOMMAND<\/tt>\/
\nSC_CLOSE<\/tt><\/td>\n		\u2190<\/td>\nClose button\/
\nAlt<\/kbd>+F4<\/kbd>\/
\nSystem menu Close<\/td>\n<\/tr>\n
 <\/td>\n <\/td>\n\u2193<\/td>\n<\/tr>\n
 <\/td>\n <\/td>\nWM_CLOSE<\/tt><\/td>\n <\/td>\nUser hits ESC<\/kbd><\/td>\n<\/tr>\n
 <\/td>\n <\/td>\n\u2193<\/td>\n <\/td>\n\u2193<\/td>\n<\/tr>\n
User clicks
\nCancel button<\/td>\n		\u2192<\/td>\nWM_COMMAND<\/tt>\/
\nBN_CLICK<\/tt>\/
\nIDCANCEL<\/tt><\/td>\n		\u2190<\/td>\nIs\u00adDialog\u00adMessage<\/tt><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

We noted at the end of that article that if you have a button whose ID is IDCANCEL<\/code>, the dialog manager will defer to that button to decide whether to allow ESC<\/kbd> key, the Close button, or other nonclient affordances to convert the corresponding action to a simulated click on that button. So the obvious way to take advantage of this is to put a Cancel button on your dialog box, and disable it when you don’t want the user to dismiss the dialog box with the ESC<\/code> key, the Close button, or other standard affordances.\u00b9<\/p>\n

Notice that everything in the diagram funnels into WM_COMMAND<\/code>\/IDCANCEL<\/code>, even if you don’t actually have a control whose ID is IDCANCEL<\/code>. If you add a handler to your dialog procedure for WM_COMMAND<\/code>, then all of the actions will come through that handler, and you can customize the behavior at that point. You could call EndDialog<\/code> to close the dialog or just return without doing anything to keep the dialog open.<\/p>\n

Now, if you have no intention of closing the dialog in response to the Close button or the system menu Close command, then you probably shouldn’t leave them enabled. You can gray those out by doing<\/p>\n

    EnableMenuItem(GetSystemMenu(hDlg, FALSE), SC_CLOSE,\r\n                   MF_BYCOMMAND | MF_DISABLED | MF_GRAYED);\r\n<\/pre>\n
Okay, but what if you want to treat the Close button differently?<\/p>\n
From the diagram, we see that the Close button goes through a WM_CLOSE<\/code> phase, so you can handle the WM_CLOSE<\/code> message in your dialog procedure to do whatever custom Close button behavior you want. If you return TRUE<\/code> from the dialog procedure, then that will mark the message as handled, and further processing will stop. if you return FALSE<\/code>, then the Def\u00adDlg\u00adProc<\/code> will turn the WM_CLOSE<\/code> into the WM_COMMAND<\/code> message as before.<\/p>\n
If you want to treat the ESC<\/kbd> key differently from a click on the Cancel button, you’ll have to intercept it on the Is\u00adDialog\u00adMessage<\/code> path. We’ll look at that next time.<\/p>\n
\u00b9 Now, you might notice that there is no requirement that the IDCANCEL<\/code> button be in the tab order, or that it even be visible. The dialog manager merely checks whether it is enabled. Therefore, you might be tempted to control these actions by disabling your (invisible, non-tabbable) IDCANCEL<\/code> button. This is sneaky, but it will probably confuse assistive technology tools, and anybody else who inspects the window hierarchy, and besides, it’s more complicated than the other alternatives presented here.<\/p>\n","protected":false},"excerpt":{"rendered":"
Intercepting the flow in your message loop.<\/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-112082","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
Intercepting the flow in your message loop.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/112082","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=112082"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/112082\/revisions"}],"predecessor-version":[{"id":112083,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/112082\/revisions\/112083"}],"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=112082"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=112082"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=112082"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}