{"id":38753,"date":"2004-06-23T07:00:00","date_gmt":"2004-06-23T07:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2004\/06\/23\/the-evolution-of-dialog-templates-32-bit-extended-templates\/"},"modified":"2004-06-23T07:00:00","modified_gmt":"2004-06-23T07:00:00","slug":"the-evolution-of-dialog-templates-32-bit-extended-templates","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20040623-00\/?p=38753","title":{"rendered":"The evolution of dialog templates – 32-bit Extended Templates"},"content":{"rendered":"

\nAt last we reach our goal, the 32-bit extended dialog template,\nknown in resource files as DIALOGEX.\nI will celebrate this with a gratuitous\ncommutative diagram<\/a>:\n<\/p>\n\n\n\n\n
\n 16-bit DIALOG\n <\/td>\n\n →<\/font><\/p>\n
32<\/div>\n<\/td>\n
\n 32-bit DIALOG\n <\/td>\n<\/tr>\n
\n ↓<\/font>\n EX\n <\/td>\n\n <\/td>\n\n ↓<\/font>\n EX\n <\/td>\n<\/tr>\n
\n 16-bit DIALOGEX\n <\/td>\n\n →<\/font><\/p>\n
32<\/div>\n<\/td>\n
\n 32-bit DIALOGEX\n <\/td>\n<\/tr>\n<\/table>\n

\nIsn’t that special.\n<\/p>\n

\nOkay, so let’s get going. The 32-bit extended dialog template\nis the 32-bit version of the 16-bit extended dialog template,\nso you won’t see any real surprises if you’ve been following along.\n<\/p>\n

\nOnce again, we start with a header, this time the 32-bit extended header.\n<\/p>\n

\nWORD  wDlgVer;      \/\/ version number - always 1\nWORD  wSignature;   \/\/ always 0xFFFF\nDWORD dwHelpID;     \/\/ help ID\nDWORD dwExStyle;    \/\/ window extended style\nDWORD dwStyle;      \/\/ dialog style\nWORD  cItems;       \/\/ number of controls in this dialog\nWORD  x;            \/\/ x-coordinate\nWORD  y;            \/\/ y-coordinate\nWORD  cx;           \/\/ width\nWORD  cy;           \/\/ height\n<\/pre>\n
\nThe first two fields serve exactly the same purpose as the 16-bit\nextended template: They identify this header as an extended dialog template.\n<\/p>\n
\nAs before, the next two fields are new.\nThe help identifier is attached to the dialog via the\n\nSetWindowContextHelpId<\/a> function,\nand the extended dialog style shouldn’t be a surprise.\n<\/p>\n
\nYou know the drill: Next come the three strings for the menu,\nclass, and dialog title.\nSince this is the 32-bit template, the strings are Unicode.\n<\/p>\n
\nAs with the 16-bit extended template, the optional custom font\nconsists of a little more information than the non-extended template:\n<\/p>\n
\nWORD wPoint;        \/\/ point size\nWORD wWeight;       \/\/ font weight\nBYTE bItalic;       \/\/ 1 if italic, 0 if not\nBYTE bCharSet;      \/\/ character set\nWCHAR szFontName[]; \/\/ variable-length\n<\/pre>\n
\nAs before, the point, weight, italic and character set are all passed\nto\n\nthe CreateFont function<\/a>.\n<\/p>\n
\nAfter the header come the dialog item templates, each of which\nmust be aligned on a DWORD boundary.\n<\/p>\n
\nDWORD dwHelpID;     \/\/ help identifier\nDWORD dwExStyle;    \/\/ window extended style\nDWORD dwStyle;      \/\/ window style\nWORD  x;            \/\/ x-coordinate (DLUs)\nWORD  y;            \/\/ y-coordinate (DLUs)\nWORD  cx;           \/\/ width (DLUs)\nWORD  cy;           \/\/ height (DLUs)\nDWORD dwID;         \/\/ control ID\nWCHAR szClassName[];\/\/ variable-length (possibly ordinal)\nWCHAR szText[];     \/\/ variable-length (possibly ordinal)\nWORD  cbExtra;      \/\/ amount of extra data\nBYTE  rgbExtra[cbExtra]; \/\/ extra data follows (usually none)\n<\/pre>\n
\nThe changes here:\n<\/p>\n