{"id":6023,"date":"2012-11-22T07:00:00","date_gmt":"2012-11-22T07:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2012\/11\/22\/the-resource-compiler-will-helpfully-add-window-styles-for-you-but-if-youre-building-a-dialog-template-yourself-you-dont-get-that-help\/"},"modified":"2012-11-22T07:00:00","modified_gmt":"2012-11-22T07:00:00","slug":"the-resource-compiler-will-helpfully-add-window-styles-for-you-but-if-youre-building-a-dialog-template-yourself-you-dont-get-that-help","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20121122-00\/?p=6023","title":{"rendered":"The resource compiler will helpfully add window styles for you, but if you're building a dialog template yourself, you don't get that help"},"content":{"rendered":"

\nA customer was having trouble with\n\nnested dialogs<\/a>.\nThey were doing something very similar to a property sheet,\nwith a main frame dialog, and then a collection of child dialogs\nthat take turns appearing inside the frame dialog\nbased on what the user is doing.\nThe customer found that if they created the child dialogs with the\nCreate­Dialog­Param<\/code> function,\neverything worked great,\nbut if they\n\nbuilt the template at run-time<\/a>,\nkeyboard navigation wasn’t working right.\nSpecifically, one of their child dialogs contained an edit control,\nand while you could put focus on it with the mouse,\nit was not possible to tab to the control.\nOn the other hand, a resource template didn’t have this problem.\nTabbing in and out worked just fine.\n<\/p>\n

\nThere is logically no difference between a resource-based dialog template\nand a memory-based one,\nbecause\n\nthe resource-based one is implemented in terms of the\nmemory-based one<\/a>.\n<\/p>\n

\nThe real problem is the memory-based template you created differs\nsomehow from the one the resource compiler generated.\n<\/p>\n

\nOne way to identify this discrepancy is simply to\n\ndo a memcmp<\/code> of the two dialog templates<\/a>,\nthe resource-based one and the memory-based one,\nand see where they differ.\nAfter all, if you want to know why your template doesn’t match the\none generated by the resource compiler,\nyou can just ask the resource compiler to generate the template<\/i>\nand then compare the two versions.\n<\/p>\n

\nInstead of explaining this, I decided to invoke my psychic powers.\n<\/p>\n

\nMy psychic powers tell me that you neglected to provide the\nWS_TAB­STOP<\/code> style to the edit control\nwhen you created your in-memory template.\n(You probably didn’t realize that you needed to do this,\nbecause the resource compile adds that style by default.)\n<\/p><\/blockquote>\n

\nWhen you use the resource compiler to generate a dialog template,\nit sets a bunch of styles by default,\ndepending on the type of control.\nFor example,\n\nEDIT­TEXT<\/code><\/a> says\n“If you do not specify a style, the default style is\nES_LEFT | WS_BORDER | WS_TABSTOP<\/code>.”\n<\/p>\n

\nNot mentioned is that the\ndefault style is in addition to the defaults for all\ncontrols:\nWS_CHILD | WS_VISIBLE<\/code>.\n<\/p>\n

\nIf you want to turn off one of the default styles for a control,\nyou do so with the NOT<\/code> keyword.\nFor example, if you write\n<\/p>\n

\n   EDITTEXT IDC_AWESOME, 10, 10, 100, 100, ES_MULTILINE | NOT WS_VISIBLE\n<\/pre>\n
\nthe resource compiler starts with the default style of\n<\/p>\n
\ndwStyle = WS_CHILD | WS_VISIBLE | ES_LEFT | WS_BORDER | WS_TABSTOP;\n<\/pre>\n
\nthen it adds ES_MULTI­LINE<\/code>:\n<\/p>\n
\ndwStyle |= ES_MULTILINE;\n\/\/ dwStyle value is now\n\/\/ WS_CHILD | WS_VISIBLE | ES_LEFT | WS_BORDER | WS_TABSTOP | ES_MULTILINE\n<\/pre>\n
\nand then it removes WS_VISIBLE<\/code>:\n<\/p>\n
\ndwStyle &= ~WS_VISIBLE;\n\/\/ dwStyle value is now\n\/\/ WS_CHILD | ES_LEFT | WS_BORDER | WS_TABSTOP | ES_MULTILINE\n<\/pre>\n
\nwhich is the final style applied to the control.\n<\/p>\n
\nThe resource compiler is trying to help you out by pre-setting\nthe styles that you probably want,\nbut if you don’t realize that those defaults are in place,\nyou may not realize that you need to provide them yourself\nwhen you don’t use the resource compiler.\nMaybe it was being too<\/i> helpful and ended up resulting in\nhelplessness.\n<\/p>\n
\nThe customer was kind enough to write back.\n<\/p>\n
\nThanks! That did the trick.\n<\/p><\/blockquote>\n
\nFor completeness, the default dialog style is\nWS_POPUP­WINDOW =\nWS_POPUP |\nWS_BORDER |\nWS_SYS­MENU<\/code>.\nIf you have a custom font, then you also get\nDS_SET­FONT<\/code>,\nand if you have a caption, then you get\nWS_CAPTION<\/code>.<\/p>\n","protected":false},"excerpt":{"rendered":"
A customer was having trouble with nested dialogs. They were doing something very similar to a property sheet, with a main frame dialog, and then a collection of child dialogs that take turns appearing inside the frame dialog based on what the user is doing. The customer found that if they created the child dialogs […]<\/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-6023","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
A customer was having trouble with nested dialogs. They were doing something very similar to a property sheet, with a main frame dialog, and then a collection of child dialogs that take turns appearing inside the frame dialog based on what the user is doing. The customer found that if they created the child dialogs […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/6023","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=6023"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/6023\/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=6023"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=6023"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=6023"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}