C / C++ / MFC

23-May-02 4:53

Say you have a dialog with 2 member controls,
a listview and a listbox and both handles WM_LEFTBUTTONDOWN.

Then you think you could set up something like this
BEGIN_MSG_MAP(CMainDlg)
CHAIN_MSG_MAP_MEMBER(moList)
CHAIN_MSG_MAP_MEMBER(moListBox)
END_MSG_MAP()

but offcourse that will not work since moList will always get to handle
the message since it is first in the list.

The next thing you think of then is to check the HWND in each
off the classes WM_LBUTTONDOWN handlers and set bHandled to FALSE and
skip processing if it does not match.
(which is a soultion that is asking for problems when you start reusing the
classes since you will often forget to do that)

And that does not work either since the HWND is not passed on to the message
handler.

Is there some good standard soultion to this?
Or do i have to dig out the HWND some way?
Or (horrible tought) have to write a BEGIN_MSG_MAP macro that passes on the HWND?

/Magnus

Tim Smith23-May-02 4:55

23-May-02 4:55

I don't think that is doing what you expect.

Take a look at contained windows and the ALT message maps if you want to handle messages sent to the controls in your dialog's message map.

Tim Smith

I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

_Magnus_23-May-02 5:05

23-May-02 5:05

You dont have to say t dont do what i expect. Smile | :)

Anyway, what i am trying is to create some standard custom controls.
And then i would like to use them by subclassing the controls on the dialog.
So i want the controls to be what they are and not some CContainedWindow members.

Surely you must be able to do that someway Confused | :confused:

or WTL looses *BIG* to MFC in that respect.

/Magnus

Tim Smith23-May-02 5:16

23-May-02 5:16

If you are trying to create standard custom controls then why are you trying to process the button down messages in dialog's main message map?

Either you use contained windows or you subclass CEdit for example and have the message map in the subclass.

Tim Smith

I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

_Magnus_23-May-02 5:24

23-May-02 5:24

I am processing the messages there because thats where they are sent.
I have subclassed the control and i have the messagemap in the subclass, but
WIN32 send messages to childwindows to the parent window.

So either i am missing a big part of the picture here or there is
not possible to create custom controls in WTL that can be reused easily. OMG | :OMG:

/Magnus

Tim Smith23-May-02 6:15

23-May-02 6:15

????

You mentioned WM_LBUTTONDOWN which shouldn't be redirected to the parent. But if you are talking about notification message, then look at the reflect macros. This will allow you to reflect the messages back to the control.

MFC does handle this a bit better. But ATL/WTL gives the the macros to do the what you need to do.

Tim Smith

I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

_Magnus_23-May-02 6:26

23-May-02 6:26

Yes i got the messages mixed up with notifications there, but
in this case even the WM_LBUTTONUP is sent to the parent and not to my
subclassed window.
It's a static control, maybe they are a special?
I remember someting (but not what) about them being special if you use the default id for them. (which i dont do in this case)

/Magnus

Tim Smith23-May-02 6:51

23-May-02 6:51

Ok, then at this point you are getting into specifics I know nothing about.

So I can't honestly contribute. Frown | :(

But if you want me to, I can try to make up crap that sounds good. Smile | :)

Tim Smith

I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

Magnus_23-May-02 7:21

Magnus_

23-May-02 7:21

Tim Smith wrote:
But if you want me to, I can try to make up crap that sounds good

Please do, can't be worse than the crap i written alreaday. Smile | :)

Thanks for the help anyway.

I think i leave this now, drown my sorrows in huge amounts of booze, and try again tomorrow.

Smile | :)

/Magnus

Joao Vaz23-May-02 23:25

Joao Vaz

23-May-02 23:25

Tim Smith wrote:
But if you want me to, I can try to make up crap that sounds good.

Your Dark side of Marketing that comes from selling your own product Laugh | :laugh:

(OK ! OK ! I admit , it was a nasty one Unsure | :~

)

Cheers,
Joao Vaz
A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)

peterchen23-May-02 8:02

peterchen

23-May-02 8:02

You need to use Contained Windows and Alternate Message Maps.

The "CContainedWindow" documentation sums this up pretty good

1) Add a member CContainedWindow m_wnd1, m_wnd2 to your class
(could also be CContainedWindow<mybaseclass>)

2) in your dlg CTor, call the CContainedWindow's CTor with
1) Window Class String for the window to create
2) this
3) a dialog-unique number, e.g. 1 and 2

3) add a message map like this:

BEGIN_MSG_MAP(CMyDialog)
   ...
   MESSAGE_HANDLER(WM_CREATE, OnCreate)
   ...
// Declare an alternate message map, identified by '1'
ALT_MSG_MAP(1)
   MESSAGE_HANDLER(WM_LBUTTONDOWN, OnLBDown_FirstControl)
// Declare an alternate message map, identified by '2'
ALT_MSG_MAP(2)
   MESSAGE_HANDLER(WM_LBUTTONDOWN, OnLBDown_SecondControl)
END_MSG_MAP()

that's it, pretty much.

The earth is not dying. It is being killed.

_Magnus_23-May-02 23:06

23-May-02 23:06

I dont want to use CContainedWindows, they are good if
you would like to do some special processing for controls without
creating a subclass class yourself, but for a control
you intend to reuse they are no good.
You cannot resue the code based on them. (not in any good way anyway)

Anyway i found out what the problem was, very easy just as long
as you look in the right place. Blush | :O

The statics have to have the SS_NOTIFY style set to recive the message.

/Magnus