Handling child window through child proc: good or bad practice

Question

4.33/5 (3 votes)

See more:

Hi all.
I'm new to the forum, new to C++ and new to windows raw programming, through win 32. I would like to know what is the best way to handle child window messages: is it any how less efficient to register individual child window proc so that i can encapsulate the whole handler in a package? Or is it better to do a little work around and add a switch to the registered parent window proc and call each child message handler?

Posted 19-May-11 17:36pm

PauloSherring

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nithin Sundar · Accepted Answer · 2011-05-19T18:50:00

I feel that having a separate procedure function for each window is best in case you might want to do something specific. Sending a message to the parent window can be done if you have some logic which requires the Parent and the child window to work together. You can have a common Window procedure if you just handle the usual messages like WM_CREATE and WM_PAINT.

This is just my opinion and I feel that others might have more information on this. Hope this helped.

Guyverthree · Accepted Answer · 2011-05-19T23:34:00

It depends on how much common behaviour there is between the two but personally, I think it's best if the child has it's own WinProc as this means that you can re-use the child window class again with a different parent class, it also makes it much more readable.

Implement messages that it sends it's parent if it requires the parent to do stuff because this way you have far more readable and reusable code in the parent as well.

Handling child window through child proc: good or bad practice

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0