{"id":36523,"date":"2005-02-04T07:01:00","date_gmt":"2005-02-04T07:01:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2005\/02\/04\/whats-the-deal-with-the-ds_shellfont-flag\/"},"modified":"2005-02-04T07:01:00","modified_gmt":"2005-02-04T07:01:00","slug":"whats-the-deal-with-the-ds_shellfont-flag","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20050204-00\/?p=36523","title":{"rendered":"What's the deal with the DS_SHELLFONT flag?"},"content":{"rendered":"

It indicates that you want the Windows 2000 default shell font. But that doesn’t mean that you’re going to get it.\n In order to indicate that you would like the “Windows 2000” look for your dialog, you have to do three things<\/a> and hope for a fourth:<\/p>\n

    \n
  1. Use a DIALOGEX<\/code> template instead of a DIALOG<\/code> template. <\/li>\n
  2. Set the DS_SHELLFONT<\/code> flag in your dialog styles. <\/li>\n
  3. Set the dialog font to “MS Shell Dlg”. <\/li>\n
  4. Hope that you’re running on Windows 2000 or later on a system that has the new Windows 2000 dialog font enabled. <\/li>\n<\/ol>\n

    If all four conditions are satisfied, then your dialog gets the “Windows 2000” look.\n If any condition fails, then you get the “classic” dialog font. Note that the fourth condition is not within your program’s control. Consequently, you have to make sure your dialog looks good in both<\/strong> the “classic” dialog font and the new one.\n For property sheet pages, things are more complicated.\n It would be visually jarring for there to be a mix of fonts on a property sheet. You wouldn’t want the “Advanced” button to be in MS Sans Serif but the “Apply” button in Tahoma. To avoid this problem, the property sheet manager looks at all the pages in the property sheet. If they are all using the “Windows 2000” look, then the property sheet uses the “Windows 2000” look also. But if there is even a single page that does not use the “Windows 2000” look, then the property sheet reverts to the “classic” look and also converts all the “Windows 2000”-look pages to “classic” look<\/strong>.\n This way, all the pages in the property sheet have the “classic” look instead of having a mishmash of some pages with the classic look and some with the Windows 2000 look.\n That’s why you will occasionally find that a shell property sheet has reverted to the “classic” look<\/a>. Some shell extension infected the property sheet with a page that does not have the “Windows 2000” look, and for the sake of visual consistency, the property sheet manager set all the pages on the property sheet to “classic” look.<\/p>\n

    This is another reason it is important that you test your property sheet pages both with the “Windows 2000” look and the “classic” look. If your property sheet page ends up sharing a property sheet with a non-“Windows 2000”-look page, your page is going to be reverted to “classic” look. <\/p>\n","protected":false},"excerpt":{"rendered":"

    It indicates that you want the Windows 2000 default shell font. But that doesn’t mean that you’re going to get it. In order to indicate that you would like the “Windows 2000” look for your dialog, you have to do three things and hope for a fourth: Use a DIALOGEX template instead of a DIALOG template. Set […]<\/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-36523","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"

    It indicates that you want the Windows 2000 default shell font. But that doesn’t mean that you’re going to get it. In order to indicate that you would like the “Windows 2000” look for your dialog, you have to do three things and hope for a fourth: Use a DIALOGEX template instead of a DIALOG template. Set […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/36523","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=36523"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/36523\/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=36523"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=36523"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=36523"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}