Home > Articles > Programming > User Interface (UI)

Creating Dynamic Drop Menus on Toolbar Buttons

📄 Contents

  1. Let's Get Started
  2. Summary
  • Print
  • + Share This
Rick Ruhl shows how easy it is to create and use dynamic drop menus on toolbar buttons using C++, with and without creating menu resources.
Like this article? We recommend

There's an old, trite saying: "Necessity is the mother of invention." Since I'm an old, trite programmer, this saying worked well for me with code I needed to write for one of our wireless applications. The application uses "snap-in" DLL technology for adding data modes to the program. All that's needed by the end user is to put a DLL in the same folder as the program, and the snap-in DLL adds this mode to its internal list. Depending on which DLLs are installed, I needed a drop-down menu off the toolbar to let the user choose the mode he or she wants, based on the DLLs that are installed.

Many articles have been written on how to write code to create and process drop menus from a toolbar button, but I couldn't find one on creating and processing dynamic menus. I knew that the functionality existed, though, so I went to the Windows API for help. This article shows you how to do both dynamic and static drop menus for two toolbar buttons.

NOTE

The important thing to remember about these drop menus is that they're menus with the pop-up style bit set. For static menus, you'll need to create them in the resource editor. With the dynamic menus, a function call will create a pop-up menu for you on the fly.

This code in C++ was used in an RF modem application where the modes could change on the fly if a DLL was added to the folder where the application resided. Therefore, we can rebuild the dynamic menu every time it's clicked, reflecting the latest additions in the snap-in DLL.

Let's Get Started

First, you need to set the toolbar for extended styles and allow the TBSYLE_EX_DRAWDARROWS to be set, so you can have an arrow on the button that will handle the drop menu:

DWORD dwExStyle = TBSTYLE_EX_DRAWDDARROWS;
m_toolbar.GetToolBarCtrl().SendMessage(TB_SETEXTENDEDSTYLE, 0, LPARAM)dwExStyle);

Next, set the button where you want to have the menu to the TBSTYLE_DROPDOWN style:

DWORD dwStyle = m_toolbar.GetButtonStyle(m_toolbar.CommandToIndex(ID_MYBUTTONWITHDYNAMICMENU);
dwStyle |= TBSTYLE_DROPDOWN;
m_toolbar.SetButtonStyle(m_hftoolbar.CommandToIndex(ID_MYBUTTONWITHDYNAMICMENU), dwStyle);

m_toolbar.GetButtonStyle(m_toolbar.CommandToIndex(ID_MYBUTONWITHSTATICMENU);
m_toolbar.SetButtonStyle(m_hftoolbar.CommandToIndex(ID_MYBUTONWITHSTATICMENU), dwStyle);

If you compile, link, and run the code now, you'll see an arrow on the button you selected to be the "chosen one."

The next step is to process the drop-down message; you can do this with the ON_NOTIFY macro and the resource ID of the toolbar:

ON_NOTIFY(TBN_DROPDOWN, IDR_HF_FRAME, OnDropDownMenu)

OnDropDownMenu is the function that will create the menu on the fly and assign dynamic or static menus to the buttons you chose. In this example, based on the toolbar button that's pressed, it either creates a dynamic drop-down menu or one based out of a static resource:

void CWindowFrame::OnDropDownMenu(UINT uint, NMHDR * pnmtb_1, LRESULT *plr)
{
   CWnd *pWnd;
   UINT nID;
   NMTOOLBAR* pnmtb = (NMTOOLBAR *) pnmtb_1;
   // which button was pressed?
   switch (pnmtb->iItem)
   {
   case ID_MYBUTTONWITHDYNAMICMENU:
     nID = ID_MYBUTTONWITHDYNAMICMENU;
     break;
   case ID_MYBUTTONWITHSTATICMENU:
     nID = ID_MYBUTTONWITHSTATICMENU;
     break;

   default:
     return;
   }

   // create the menu
   CMenu * menu;
   menu = new CMenu;
   switch (nID)
   {
   case ID_MYBUTTONWITHDYNAMICMENU:
     menu->CreatePopupMenu();  // create the popup menu dynamically
        for (int i=0;i<64;i++)
     {
        if (m_hhmodearray[i].mode !=0)
        {
   menu->AppendMenu(MF_STRING,WM_USER+32767+i,m_hhmodearray[i].modename);
        }
     }
     break;
   case ID_MYBUTTONWITHSTATICMENU:
     menu->LoadMenu(IDR_STAIC_MENU); // create the popup menu with a static resource.
     menu=menu->GetSubMenu(0);
     break;
   }


   ASSERT(pPopup);

   CRect rc;
   ::SendMessage(m_toolbar.m_hWnd,TB_GETRECT, pnmtb->iItem, (LPARAM)&rc);
   m_toolbar.ClientToScreen(&rc);

   menu->TrackPopupMenu( TPM_LEFTALIGN | TPM_LEFTBUTTON | TPM_VERTICAL,
     rc.left, rc.bottom, this, &rc);
}

In the code above, the first thing we need to do is typecast the NMHDR * parameter to an NMTOOLBAR * datatype. This gives us access to the toolbar.

Now, based on which button is pressed, we create the pop-up menu. I move it into a variable for processing, just in case the pnmtb->iItem gets changed. If the button is for the static menu, we get it from the menu resource that we created in the resource editor. If the button pressed is for the dynamic menu, that's where the interesting code is.

In the above case, in the init code, I loaded string names and ID numbers from a DLL into an array of 64 structures. Because the DLL changes those strings and ID numbers on the fly, using dynamic menus allows us to change the menus on the fly, when the DLL changes. Since I have an array of string names and modem IDs, I can use it to create the dynamic menus and associated IDs.

Now we need to add the menus and their dynamic resource IDs to the drop menu. We do this with the function call AppendMenu:

menu->AppendMenu(MF_STRING,WM_USER+32767+i,m_hhmodearray[i].modename);

I use a FOR loop around the code so I can iterate each string name and set up the dynamic IDs.

CAUTION

Make sure that the number you choose to create the dynamic IDs isn't equivalent to any you've already defined with WM_USER. I chose 32,767 as an arbitrary number.

The TrackPopUpMenu function, since it's assigned to that button on the toolbar, displays a shortcut menu at the specified location and tracks the selection of items on the menu. This way, your menu pops up on the toolbar and is able to process the dynamic IDs associated with it.

Now I can use the ON_COMMAND_RANGE macro to see whether one of those dynamic IDs was hit when the menu was clicked:

ON_COMMAND_RANGE(WM_USER+32767,WM_USER+32767+64,DoFunction)

And then use DoFunction to process whichever command it was:

void CHfWindowFrame::DoFunction(UINT mode)
{

   int i = mode - (WM_USER+32767);
   HamHubMode(m_hhmodearray[i].modename,m_hhmodearray[i].mode);
}

I subtract WM_USER+32767 from the menu ID and get the mode number for the DLL; then I make the call to the DLL with the correct mode and mode name in the array. You can modify this code as needed for your dynamic and static drop menus.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020