{"id":108952,"date":"2023-11-01T07:00:00","date_gmt":"2023-11-01T14:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=108952"},"modified":"2023-11-01T06:47:55","modified_gmt":"2023-11-01T13:47:55","slug":"20231101-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20231101-00\/?p=108952","title":{"rendered":"More notes on use of the DS_CONTROL<\/CODE> style"},"content":{"rendered":"

Here’s a follow-up on some old articles on the DS_CONTROL<\/code> dialog style<\/a> and avoiding accidental control ID collisions<\/a>.<\/p>\n

When you add the DS_CONTROL<\/code> style to your dialog template, there are other changes to the dialog styles which come into play. Some are mandatory, some are automatic, and some are optional.<\/p>\n

Mandatory<\/b>: You must<\/i> remove the WS_POPUP<\/code> style and you must<\/i> add the WS_CHILD<\/code> style. If you omit the WS_CHILD<\/code> style or accidentally specify the WS_POPUP<\/code> style, then the dialog won’t be created as a child window of the parent window you specified.<\/p>\n

Automatic<\/b>: You may<\/i> remove the WS_CAPTION<\/code> and WS_SYS\u00adMENU<\/code> styles. The dialog manager removes them automatically, so this isn’t a requirement, but you are welcome to remove them yourself, either to avoid confusion or out of a sense of cleanliness.<\/p>\n

Optional<\/b>: You have the option of adding or removing the WS_VISIBLE<\/code> and DS_MODAL\u00adFRAME<\/code> styles, depending on the behavior you desire.<\/p>\n

If you specify WS_VISIBLE<\/code>, then the child dialog will be created visible. Otherwise, it will be created hidden.<\/p>\n

If you specify DS_MODAL\u00adFRAME<\/code>, then the child dialog gets the WS_EX_WINDOW\u00adEDGE<\/code> extended style, which gives it an extra outer edge border. If you want the child dialog to blend in seamlessly with its parent, then you probably want to remove that style.<\/p>\n","protected":false},"excerpt":{"rendered":"

Styles that have to go in, and styles that have to come out. (And styles that you can choose.)<\/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-108952","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"

Styles that have to go in, and styles that have to come out. (And styles that you can choose.)<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/108952","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=108952"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/108952\/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=108952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=108952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=108952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}