I need to disable the menu items that are not applicable at various places in the application.
The command messages are not being routed through the OnUpdate handlers.
I have looked at a few issues that talk about this. For example using "this" on the following does not work:
pPopup->TrackPopupMenu(TPM
Attaching it to the mainframe does something but still not going through the handlers
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Instead of
CWnd* pWnd = GetParent()->GetParent()->Ge
pPopup->TrackPopupMenu(TPM_
this);
try to use
CWnd* pWnd = GetParentFrame();
pPopup->TrackPopupMenu(TPM_
pWnd);
See GetParentFrame details at
http://msdn.microsoft.com/
I tried that and a frame window is returned but when I use it all the menu items are greyed out meaning that it can't find the message handlers that are working now in the tree. The frame window is to the property dialog box that contains the tree.
My question is why can it find all the message handlers for the messages them selles but not on the OnUpdate messages. It doesn't make sense.
Is there a way to redirect whatever messages to the tree itself?
For what it's worth:
I just looked at the source code for an old SDI project of mine. It pops up a context menu when clicking on an item in a CTreeView-derived pane. The enabling is done in the ON_UPDATE_COMMAND_UI handlers, and items are correctly enabled or disabled according to the specific context at the time of the pop up.
All I can say is that it does work as advertised in the MFC documentation. I use:
AfxGetApp()->m_pMainWnd
as the CWnd pointer in the fourth parameter in the TrackPopupMenu call (it is the pointer to my CFrameWnd-derived object. In that module, CMainFrame, I have message map entries for both ON_COMMAND and ON_UPDATE_COMMAND_UI for each item in the popup menu.
My code in the CTreeView-derived object looks almost identical to yours (before you added the manual enabling). All I can suggest is that you examine the actual values of constants such as ID_POPUP_MOVESUBTREE and see if they are unique (examine your resource.h file). Also, each of my menu item command IDs is higher than 1000 (I vaguely recall that there was an issue with context help or something). If you are not using CView- and CFrameWnd-derived objects, that might also affect the behavior.
In my case, the MainFrame gets a WM_INITMENUPOPUP message and breakpoints in the updateUI handlers immediately get hit.
I tried using the main frame also. The menu changed completely with many greyed out options and some enabled functions. It was as if the main frame had other items it found with similar ID values. IN this case the tree is in a DLL so it is possible that some of the IDs are the same as in the main app.
But more importantly is it customary to use the main window then?
What is happening and how should I setup my handlers. None of the handlers seem to have been called in the tree class itself which currently works the way I coded it.
It is the code in
CFrameWnd::OnInitMenuPopup
that cycles through the menu and calls the OnUpdateXxxx for each item.
CWnd::OnInitMenuPopup
You can add a handler for WM_INITMENUPOPUP in some other window (such as your tree control). It could be menu-specific (rather than generalized as is the one in CFrameWnd). But it's lots more work, in that you need to decode the message parameters, walk the menu tree, etc.
So yes... it is customary (if not required) to put command handlers, and UI update handlers in the main frame. If doing so casues other menu items to be disabled unexpectedly, then you need to add command handlers and ui update handlers for them.
Business Accounts
Answer for Membership
by: DanRollinsPosted on 2009-04-25 at 18:08:39ID: 24234128
Have you seen this article:
When Update Handlers Are Called
http://msdn.microsoft.com/
I can't tell from your code, but... there has to be an ON_UPDATE_COMMAND_UI entry and (this is the most common oversight) there must also be an ON_COMMAND entry somewhere with the same command ID
Also, command UI is usually in the MainFrame, so that's what you will typically used as the owning window in the TrackPopupMenu call