To be clear: I had message handlers in my view class for menu commands and toolbar buttons. When I used the MFC dialog bar, I found that if I gave a control (a button) the same resource ID as a menu command or toolbar button, I could click the menu command, the tollbar button, or the button in the dialog bar and have the same code (the message handler in my view) do whatever needed to be done.

 

When I switched to the CodeJock CXTPDialogBar, this stopped working. I wanted to quickly find a way to get things working again, and they do. I'd like to do things in a better way, if possible. However, I tried your code an nothing happens. I click the button in the dialog bar and the handler in my view class doesn't get the message. I'm not sure how it would...

 

I'm obviously not an expert in command routing. Any more pointers on what I can try? Do you know if one of the CodeJock examples shows the correct way to do this?

 

If a WM_COMMAND message does not arrive to its destination, it is due to an erroneous message handler: CWnd::OnCmdMsg. If the main-window does not route messages to the CXTPDialogBar, then you cannot expect it to receive them. WM_COMMAND is propagated from top to bottom, so you should NEVER send it to a window's parent window! Doing so might hang your application if some other programmer, later on, implements command routing logic the right way:

 

BOOL CMainWnd::OnCmdMsg(...)

{

     if (m_wndDialogBar.OnCmdMsg(...))

         return TRUE;

 

     return CFrameWnd::OnCmdMsg(...);

}

 

This is of course a very simple example. Usually you have to consider focus, active pane/view and stuff. The reason why CDialog worked out of the box, is that MFC does a lot of nasty things behind your back :)

 

 

Note: If you must send a WM_COMMAND message, then always send it to the top-level parent, usually AfxGetMainWnd().