bcs0228
asked on
Problem with Dialog Bar Message Map
I have developed my own sticky button class (CColourButton) derived from
CButton. When the button is clicked on with the mouse it pushes in and stays
pushed in. It is also repainted in a certain colour. When the button is
clicked on again it pops back out and is repainted in the standard button
colours.
The class works great when I subclass the CColourButton class to button controls
in a dialog application.
Problems occur though when I subclass the CColourButton class to button controls
in a dialog bar (CDialogBar). The dialog bar is attached to the frame of an
SDI application. Each time the mouse is clicked on a button, the CColourButton
class receives two BN_CLICKED notifications.
The CColurButton class is described below:
I am using message reflection so that my button class can handle the
BN_CLICKED notification message. It is from within the BN_CLICKED
notification handler that I determine whether to keep the button pushed in
or to pop it out.
Message reflection has been set up by adding the ON_CONTROL_REFLECT_EX macro
to the CColourButton message map as follows:
ON_CONTROL_REFLECT_EX(BN_C
ON_CONTROL_REFLECT_EX is used instead of ON_CONTROL_REFLECT because I want
the owner of the button control to be able to process BN_CLICKED messages as
well.
The OnClicked() member function is as follows:
BOOL CMyButton::OnClicked()
{
// TODO: Add your control notification handler code here
// Does some processing....
return FALSE; // Returning false ensures that the parent also gets
to see the
// BN_CLICKED message
}
Can someone please explain why I am receiving two BN_CLICKED messages when
subclassing to a button control in a dialog bar?
I believe there may be some problem with the dialog bar message map which is causing two BN_CLICKED messages to be posted each time the button is clicked.
Regards
Martin Hinchy
CButton. When the button is clicked on with the mouse it pushes in and stays
pushed in. It is also repainted in a certain colour. When the button is
clicked on again it pops back out and is repainted in the standard button
colours.
The class works great when I subclass the CColourButton class to button controls
in a dialog application.
Problems occur though when I subclass the CColourButton class to button controls
in a dialog bar (CDialogBar). The dialog bar is attached to the frame of an
SDI application. Each time the mouse is clicked on a button, the CColourButton
class receives two BN_CLICKED notifications.
The CColurButton class is described below:
I am using message reflection so that my button class can handle the
BN_CLICKED notification message. It is from within the BN_CLICKED
notification handler that I determine whether to keep the button pushed in
or to pop it out.
Message reflection has been set up by adding the ON_CONTROL_REFLECT_EX macro
to the CColourButton message map as follows:
ON_CONTROL_REFLECT_EX(BN_C
ON_CONTROL_REFLECT_EX is used instead of ON_CONTROL_REFLECT because I want
the owner of the button control to be able to process BN_CLICKED messages as
well.
The OnClicked() member function is as follows:
BOOL CMyButton::OnClicked()
{
// TODO: Add your control notification handler code here
// Does some processing....
return FALSE; // Returning false ensures that the parent also gets
to see the
// BN_CLICKED message
}
Can someone please explain why I am receiving two BN_CLICKED messages when
subclassing to a button control in a dialog bar?
I believe there may be some problem with the dialog bar message map which is causing two BN_CLICKED messages to be posted each time the button is clicked.
Regards
Martin Hinchy
If you post your project somwhere I can take a look
I can try a try if you email your sample to me at chenbo@supresoft.com.
ASKER
To speedup:
I have emailed my sample code to you.
To lucidity:
Let me know where you want the sample code posted or emailed.
I have emailed my sample code to you.
To lucidity:
Let me know where you want the sample code posted or emailed.
Martin,
Did you get an answer on this one. I'm using dialog bars "all over town" in my code and have never had the problem you describe. If you want, email me a copy and I'll see what I can do.
Tom Archer
Did you get an answer on this one. I'm using dialog bars "all over town" in my code and have never had the problem you describe. If you want, email me a copy and I'll see what I can do.
Tom Archer
ASKER
Tom,
I haven't been able to get an answer on this from anyone and I have posted the problem to numerous newsgroups and discussion boards.
What's your email address so I can email the code to you.
Regards
Martin
I haven't been able to get an answer on this from anyone and I have posted the problem to numerous newsgroups and discussion boards.
What's your email address so I can email the code to you.
Regards
Martin
Hi Martin,
It's tma-ng@mindspring.com
Tom
It's tma-ng@mindspring.com
Tom
ASKER
Tom,
The code is on its way.
Regards
Martin
The code is on its way.
Regards
Martin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
To Lucidity,
I don't really want to have one CColourButton class for dialog windows and another one for dialog bars. I'd rather just have one common class.
Your second option re: overriding the main window class sounds preferable. Can you please explain what you mean. Do you mean trapping all windows messages in CMainFrame using OnWndMsg()?
I don't really want to have one CColourButton class for dialog windows and another one for dialog bars. I'd rather just have one common class.
Your second option re: overriding the main window class sounds preferable. Can you please explain what you mean. Do you mean trapping all windows messages in CMainFrame using OnWndMsg()?