{"id":265,"date":"2009-07-12T23:26:10","date_gmt":"2009-07-12T17:56:10","guid":{"rendered":"http:\/\/techtwaddle.net\/?p=265"},"modified":"2011-04-12T23:26:27","modified_gmt":"2011-04-12T17:56:27","slug":"fun-with-menus","status":"publish","type":"post","link":"https:\/\/techtwaddle.co.in\/blog\/2009\/07\/12\/fun-with-menus\/","title":{"rendered":"Fun with menus!"},"content":{"rendered":"
I received a comment on one of my previous <\/span>posts<\/a>, correcting me on what I had mentioned. The menu bar resource was defined as below:<\/span><\/div>\n



\n<\/font>IDR_MENU SHMENUBAR DISCARDABLE<\/span>

\nBEGIN<\/span>

\n    IDR_MENU, <\/span>

\n    2,<\/span>

\n

\n    I_IMAGENONE, IDM_OK, TBSTATE_ENABLED, TBSTYLE_BUTTON | TBSTYLE_AUTOSIZE,<\/span>

\n    IDS_OK, 0, NOMENU,<\/span>

\n    <\/span>

\n    I_IMAGENONE, IDM_HELP, TBSTATE_ENABLED, TBSTYLE_DROPDOWN | TBSTYLE_AUTOSIZE,<\/span>

\n    IDS_HELP, 0, 0,<\/span>

\nEND<\/span><\/font><\/p>\n

And I had said, <\/span>"<\/span>Everything in between BEGIN and END defines the menu bar. The first line under BEGIN<\/font> should be the same as the menu bar identifier, IDR_MENU<\/span>"<\/span>. Well, I was wrong there. The first line under <\/span>BEGIN<\/span> <\/span>could be same as the menu bar identifier but it need not be. Thanks <\/span>Binary<\/a> for noticing that! The first line under <\/span>BEGIN<\/span> <\/span>is the identifier of the popup menu that appears when the user clicks on one of the popup menus.  If both the softkeys in your menu bar are buttons then the popup menu identifier could be specified as zero. So the correct way of doing it would be to define the menu bar as:<\/span><\/div>\n

\nIDR_MENU SHMENUBAR DISCARDABLE<\/span>

\nBEGIN<\/span>

\n    IDR_MENU_POPUP, <\/span>

\n    2,<\/span>

\n

\n    I_IMAGENONE, IDM_OK, TBSTATE_ENABLED, TBSTYLE_BUTTON | TBSTYLE_AUTOSIZE,<\/span>

\n    IDS_OK, 0, NOMENU,<\/span>

\n    <\/span>

\n    I_IMAGENONE, IDM_HELP, TBSTATE_ENABLED, TBSTYLE_DROPDOWN | TBSTYLE_AUTOSIZE,<\/span>

\n    IDS_HELP, 0, 0,<\/span>

\nEND<\/span><\/font><\/p>\n

and <\/span>IDR_MENU_POPUP<\/span> is defined as a popup menu,<\/span><\/div>\n

\nIDR_MENU_POPUP MENU <\/span>

\nBEGIN<\/span>

\n    POPUP ""<\/span>

\n    BEGIN<\/span>

\n        MENUITEM "System Metric",               IDM_SYSTEM_METRIC<\/span>

\n        MENUITEM "About",                              IDM_HELP_ABOUT<\/span>

\n    END<\/span>

\nEND<\/span><\/p>\n

In the above menu bar, the left softkey is an "OK" button and right softkey is a popup menu with "System Metric" and "About" as its menu items. Just remember that <\/span>IDR_MENU<\/span> is the identifier of the softkey bar which is created and <\/span>IDR_MENU_POPUP<\/span> is the identifier of the popup menu, which appears when the user clicks on the right softkey "Menu"<\/span><\/div>\n

 <\/p>\n

Binary also raised another interesting point. How do we get popup menus on both right softkey and left softkey? Of course, the first thing I did was to remove the <\/span>NOMENU<\/span> option from the part defining the left softkey. You can see the problem there can’t you? Both left softkey and right softkey become popup menus, but both the popup menus show the same menu items because we specified a single popup menu identifier, <\/span>IDR_MENU_POPUP<\/span>, and that is why the same popup menu shows up for both the softkeys.<\/span><\/div>\n

\"\"\n<\/p>\n

I was looking into how to get different popup menus for the 2 softkeys when Mr (or Ms) Binary replied again. Binary had figured out how.<\/span><\/div>\n

 <\/p>\n

You define the popup menu as usual but with two popup entries,<\/span><\/div>\n

\nIDR_MENU_POPUP MENU <\/span>

\nBEGIN<\/span>

\n    POPUP "Menu L"<\/span>

\n    BEGIN<\/span>

\n        MENUITEM "Menu Item1",                        0<\/span>

\n        MENUITEM "Menu Item2",                        0<\/span>

\n    END<\/span>

\n

\n    POPUP "Menu R"<\/span>

\n    BEGIN<\/span>

\n        MENUITEM "System Metric",               IDM_SYSTEM_METRIC<\/span>

\n        MENUITEM "About",                              IDM_HELP_ABOUT<\/span>

\n    END<\/span>

\nEND<\/span>
\n <\/p>\n

and while creating the menubar in <\/span>WM_CREATE<\/span> message, specify the following options,<\/span><\/div>\n

\n        case WM_CREATE:<\/span>

\n            SHMENUBARINFO mbi;<\/span>

\n

\n            memset(&mbi, 0, sizeof(SHMENUBARINFO));<\/span>

\n            mbi.cbSize     = sizeof(SHMENUBARINFO);<\/span>

\n            mbi.hwndParent = hWnd;<\/span>

\n            mbi.nToolBarId = IDR_MENU_POPUP;<\/span><\/span>

\n            mbi.hInstRes   = g_hInst;<\/span>

\n            mbi.dwFlags = SHCMBF_HMENU;<\/span><\/span>

\n

\n            if (!SHCreateMenuBar(&mbi)) <\/span>

\n            {<\/span>

\n                g_hWndMenuBar = NULL;<\/span>

\n            }<\/span>

\n            else<\/span>

\n            {<\/span>

\n                g_hWndMenuBar = mbi.hwndMB;<\/span>

\n            }<\/span><\/p>\n

The only difference is we specify the popup menu identifier for <\/span>nToolBarId<\/span> member instead of the menu bar identifier and we also set the <\/span>SHCMBF_HMENU<\/span> flag. When <\/span>SHCMBF_HMENU<\/span> flag is not specified then the <\/span>nToolBarId<\/span> value is treated as a toolbar identifer which creates our usual softkey bar with left and right softkeys. If the flag is set then nToolBarId<\/span> is treated as a menu identifier. Just a regular menu bar with menus and submenus. So now when you run the application you get,<\/span><\/div>\n

\"\"<\/p>\n

Be sure to specify the message value if you want to handle these menu clicks. I have specified zero above because I am not really interested in handling these items.<\/span><\/div>\n

 <\/p>\n

So now a question pops up (pun intended), what if I have several popup menus and submenus in the popup identifier. Will it take only the first two and display them or will it do something strange? See for yourself, I used the following popup menu just for the sake of it,<\/span><\/div>\n

\nIDR_MENU_POPUP MENU <\/span>

\nBEGIN<\/span>

\n

\n    POPUP "File"<\/span>

\n    BEGIN<\/span>

\n        MENUITEM "&Open",               0<\/span>

\n        MENUITEM "&Save",                0<\/span>

\n        MENUITEM "E&xit",                  0<\/span>

\n    END<\/span>

\n

\n    POPUP "Edit"<\/span>

\n    BEGIN<\/span>

\n        MENUITEM "&Copy",               0<\/span>

\n        MENUITEM "C&ut",                 0<\/span>

\n        MENUITEM "&Paste",              0<\/span>

\n    END<\/span>

\n

\n    POPUP "View"<\/span>

\n    BEGIN<\/span>

\n        MENUITEM "&Full Screen",       0<\/span>

\n        MENUITEM "&Options",            0<\/span>

\n    END<\/span>

\n

\n    POPUP "Help"<\/span>

\n    BEGIN<\/span>

\n        MENUITEM "Abou&t",              0<\/span>

\n        MENUITEM "He&lp",                0<\/span>

\n    END<\/span>

\n

\nEND<\/span><\/p>\n



\nhere’s what is does,<\/span>
<\/p>\n

\"\"<\/p>\n

and,<\/span><\/p>\n

\n\"\"\n<\/p>\n

I have never seen that on a ppc! I was surprised that it actually works and creates a full fledged menu bar with several menus. And notice the SIP button has moved to the right. The color of the menu bar has changed as well. A pretty interesting find, I would say.<\/span><\/div>\n

\nUpdate:
\nYou might also be interested in this post, Fun with menus – part II<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I received a comment on one of my previous posts, correcting me on what I had mentioned. The menu bar resource was defined as below: IDR_MENU SHMENUBAR DISCARDABLE BEGIN     IDR_MENU,     2,     I_IMAGENONE, IDM_OK, TBSTATE_ENABLED, TBSTYLE_BUTTON | TBSTYLE_AUTOSIZE,     IDS_OK, 0, NOMENU,         I_IMAGENONE, IDM_HELP, TBSTATE_ENABLED, TBSTYLE_DROPDOWN | TBSTYLE_AUTOSIZE,     IDS_HELP, 0, … Continue reading Fun with menus!<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[1],"tags":[],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p1ktFF-4h","_links":{"self":[{"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/posts\/265"}],"collection":[{"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/comments?post=265"}],"version-history":[{"count":1,"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/posts\/265\/revisions"}],"predecessor-version":[{"id":266,"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/posts\/265\/revisions\/266"}],"wp:attachment":[{"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/media?parent=265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/categories?post=265"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techtwaddle.co.in\/blog\/wp-json\/wp\/v2\/tags?post=265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}