We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

Menus not updated in dialog application

duncan2
duncan2 asked
on
Medium Priority
395 Views
Last Modified: 2013-11-19
I have a dialog app with a menu bar and a system menu.  My UPDATE_COMMAND_UI message handlers don't do anything.  Even the system menu items don't get updated (grayed out) like they do in a doc/view application.  Thanks for your help.
Comment
Watch Question

Commented:
The problem I think your dialog is not sent WM_IDLEUPDATECOMMANDUI message. This message is MFC private message defined in afxpriv.h and is broadcast to all child window by main frame window using SendMessageToDescendnts. This is done from CWinApp::OnIdle function winch is called on idle time. I suppose you created your dialog with WM_POPUP style or it is modal so this message is not sent to it. I suggest you store pointer to your dialog somewhere, implement handler on WM_IDLEUPDATECOMMANDUI message in your dialog parent\owner class and explicity call pDialog->SendMessage(WM_IDLEUPDATECOMMANDUI)and pDialog->SendMessageToDescendants(WM_IDLEUPDATECOMMANDUI) the second function is required id your dialog class has any control bars.

Author

Commented:
I need to clarify my problem.  You suggest that I may not be getting messages to my dialog, but my message handlers are in the app.  I started with a dialog app created with app-wizard.  If you make a new dialog app, add a menu resource and add it to the dialog with dialog editor, you will see that the system menu items that should be grayed out are not.  The class wizard will not let you add message handlers for the menus in the dialog class, but you can in the app.  So the handlers in my app simply call functions in the dialog class.  When you click on a menu item these functions are called and work fine.  I also have a timer in my dialog class and it receives WM_TIMER messages fine.  So even though the dialog is created in InitInstance with DoModal, the message loop seems to be running.  Only the UPDATE_COMMAND_UI messages don't seem to work.  And they only have to get to the app, not the dialog.  Do you have any other ideas? (I am using VC 4.0).
That is because MFC framework never supports the Update
Command UI on dialog boxes

COMMAND_UI functions are implemented by a kind of neat
trick in MFC in the CFrameWnd class, Since Dialog box
have no frame whatsoever, they have no Command UIs

When a user clicks on any menu, windows before
preparing the menu sends application

WM_INITMENUPOPUP message, One of the parameter word
identifies it as a system Menu

You can do either of the following two

Handle WM_INITMENUPOPUP and do all your updateUI logic
there

or copy and tweak the handler from MFC supplied source file
WINFRM.CPP (look for OnInitMenuPopup)

If you need further help you can reach me
at
cdjindia@hotmail.com
or
cdjindia@bestweb.net




In the MFC Source code, look for handlere
If you want to do that you have to provide
Engineer
Commented:
Handle OnKickIdle to call AfxGetApp()->OnIdle(0);

The application is not getting any idle messages which does the updating of menus.


Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.