\nas I had originally written<\/A>)\nthe code has been in existence.\n<\/P>\n\nUnlike the classic menu, there is a prefix structure that\ncomes before the list of menu items.\n<\/P>\n
\nstruct MENUPREFIX16 {\n DWORD dwContextHelpID;\n};\n<\/PRE>\n\nNew to extended menus is the addition of context help IDs.\nThese values can be set and retrieved\nprogrammatically with the\nGetMenuContextHelpId<\/CODE> and\nSetMenuContextHelpId<\/CODE> functions.\n<\/P>\n\nThe template then continues with a packed array of structures\nI will call MENUITEMEX16<\/CODE>:\n<\/P>\n\nstruct MENUITEMEX16 {\n DWORD dwType;\n DWORD dwState;\n WORD wID;\n BYTE bFlags;\n CHAR szText[]; \/\/ null terminated ANSI string\n};\n<\/PRE>\n\nWhereas the members of the classic MENUITEM16<\/CODE>\nwere designed to be passed to the function\nInsertMenu<\/CODE>,\nthe members of the extended MENUITEMEX16<\/CODE> were\ndesigned to be passed to the function\nInsertMenuItem<\/CODE>.\nThe dwType<\/CODE>, dwState<\/CODE>, and\nwID<\/CODE> members correspond to\nthe fType<\/CODE>, fState<\/CODE>, and\nwID<\/CODE>\nmembers of the 16-bit MENUITEMINFO<\/CODE> structure.\nSimilarly, the szText<\/CODE> goes into the\ndwItemData<\/CODE> if the item requires a string.\n(If the item doesn’t require a string, then the\nszText<\/CODE> should be an empty string; i.e.,\nshould consist solely of the null terminator.)\n<\/P>\n\nNotice that a new feature of extended menus is that pop-up menus\ncan have IDs as well as normal menu items.\n<\/P>\n
\nThe bFlags<\/CODE> describes other information about the\nmenu item,\ninformation that in the classic menu was hidden in spare bits\nin the wFlags<\/CODE>.\nBut here, the bFlags<\/CODE> is where this information is kept.\nThe following flags are currently defined:\n<\/P>\n\n0x01<\/CODE><\/TD>| This item is a pop-up submenu<\/TD><\/TR>\n | 0x80<\/CODE><\/TD>| This item is the last item in the menu<\/TD><\/TR>\n<\/TABLE>\n \nIf indeed the bottom bit is set, then after the MENUITEMEX16<\/CODE>\ncomes a description of the submenu, recursively.\n(Note that the submenu does not have\na MENUHEADER16<\/CODE>.)\n<\/P>\n\nAs before, we’ll illustrate this format with an example.\n<\/P>\n \n1 MENUEX 1000\nBEGIN\n POPUP “&File”, 200,,, 1001\n BEGIN\n MENUITEM “&Open\\tCtrl+O”, 100\n MENUITEM “”, -1, MFT_SEPARATOR\n MENUITEM “&Exit\\tAlt+X”, 101\n END\n POPUP “&View”, 201,,, 1002\n BEGIN\n MENUITEM “&Status Bar”, 102,, MFS_CHECKED\n END\nEND\n<\/PRE>\n\nThe resulting 16-bit extended menu template begins with the header:\n<\/P>\n \n0000 01 00 \/\/ wVersion = 1\n0002 04 00 \/\/ cbHeaderSize = 4\n<\/PRE>\n\nSince this is the start of a menu, we get a context help ID:\n<\/P>\n \n0004 E8 03 00 00 \/\/ dwContextHelpID = 1000\n<\/PRE>\n\nAfter the context help ID come the menu items.\nOur first is a pop-up submenu,\nso the bFlags<\/CODE> indicates that a submenu is coming:\n<\/P>\n\n0008 00 00 00 00 \/\/ dwType = MFT_STRING\n000C 00 00 00 00 \/\/ dwState = 0\n0010 C8 00 \/\/ wID = 200\n0012 01 \/\/ bFlags = “pop-up submenu”\n0013 26 46 69 6C 65 00 \/\/ “&File” + null terminator\n<\/PRE>\n\nSince we have a pop-up submenu, we recursively include\na template for that submenu directly after the menu item template.\nConsequently, we begin with the context help ID:\n<\/P>\n \n0019 E9 03 00 00 \/\/ dwContextHelpID = 1001\n<\/PRE>\n\nAnd then the contents of the submenu:\n<\/P>\n \n001D 00 00 00 00 \/\/ dwType = MFT_STRING\n0021 00 00 00 00 \/\/ dwState = 0\n0025 64 00 \/\/ wID = 100\n0027 00 \/\/ bFlags = 0\n0028 26 4F 70 65 6E 09 43 74 72 6C 2B 4F 00\n \/\/ “&Open\\tCtrl+O” + null terminator<\/p>\n0035 00 08 00 00 \/\/ dwType = MFT_SEPARATOR\n0039 00 00 00 00 \/\/ dwState = 0\n003D FF FF \/\/ wID = -1\n003F 00 \/\/ bFlags = 0\n0040 00 \/\/ “”<\/p>\n 0041 00 00 00 00 \/\/ dwType = MFT_STRING\n0045 00 00 00 00 \/\/ dwState = 0\n0049 65 00 \/\/ wID = 101\n004B 80 \/\/ bFlags = “this is the last menu item”\n004C 26 45 78 69 74 09 41 6C 74 2B 58 00\n \/\/ “&Exit\\tAlt+X” + null terminator\n<\/PRE>\n \nWhen we reach the end of the pop-up submenu, we \npop up a level.\nTherefore, the next entries describe more top-level menu items.\n<\/P>\n \n0058 00 00 00 00 \/\/ dwType = MFT_STRING\n005C 00 00 00 00 \/\/ dwState = 0\n0060 C9 00 \/\/ wID = 201\n0062 81 \/\/ bFlags = “pop-up submenu” |\n \/\/ “this is the last menu item”\n0063 26 56 69 65 77 00 \/\/ “&View” + null terminator\n<\/PRE>\n\nAh, no sooner do we pop up than we push back down with\nanother submenu.\nAnd the “last menu item” flag is set,\nwhich means that once the submenu is finished,\nwe are done with the extended menu template.\n<\/P>\n \n0069 EA 03 00 00 \/\/ dwContextHelpID = 1002<\/p>\n006D 00 00 00 00 \/\/ dwType = MFT_STRING\n0071 08 00 00 00 \/\/ dwState = MFS_CHECKED\n0075 66 00 \/\/ wID = 102\n0077 80 \/\/ bFlags = “this is the last menu item”\n0078 26 53 74 61 74 75 73 20 42 61 72 00\n \/\/ “&Status Bar” + null terminator\n<\/PRE>\n \nAfter the context help ID, we have the sole menu item for\nthis pop-up submenu, so the first item is also the last item.\n<\/P>\n \nNext time, we’ll wrap up by looking at the final menu template format,\nthe 32-bit extended menu.\nI bet you all can’t wait.\n<\/P><\/p>\n","protected":false},"excerpt":{"rendered":" Windows 95 introduced a new menu format, known as “extended menus”. You declare these in a resource file with the MENUEX keyword. The 16-bit extended menu is really just a temporary stopping point on the way to the 32-bit extended menu, since the 16-bit form is supported only by the Windows 95 family of operating systems. It’s […]<\/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":[2],"class_list":["post-21613","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-history"],"acf":[],"blog_post_summary":" Windows 95 introduced a new menu format, known as “extended menus”. You declare these in a resource file with the MENUEX keyword. The 16-bit extended menu is really just a temporary stopping point on the way to the 32-bit extended menu, since the 16-bit form is supported only by the Windows 95 family of operating systems. It’s […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/21613","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=21613"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/21613\/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=21613"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=21613"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=21613"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} | | |