MFC Deriving my own class

Question

0.00/5 (No votes)

See more:

Hi,

I am creating my own UI component in MFC. I derived it from CWnd class and I am going to override OnPaint() method. My question concerns the method Create(), that is inherited from CWnd . I would like to know if it is good to call that from the constructor (perhaps not, because virtual methods shall not be called while creation) or I shall let the client of the class to call the Create() method on his own (which I dont like)...

Thanks for your opinions.

Best regards,
J.K.

Posted 1-Jun-13 6:47am

Kucera Jan

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)

Espen Harlinn · Accepted Answer · 2013-06-01T07:36:00

Solution 1

I'm afraid you should use the Create approach: General Window Creation Sequence[^]

Best regards
Espen Harlinn

Posted 1-Jun-13 7:36am

Espen Harlinn

Comments

Sergey Alexandrovich Kryukov 11-Jun-13 19:42pm

Good link, a 5.
—SA

Espen Harlinn 12-Jun-13 15:43pm

Thank you, Sergey :-D

nv3 · Accepted Answer · 2013-06-01T07:40:00

MFC's philosophy is a 2-step creation process, so a separation of constructor and create call. I would just stick with that for reasons of presenting a consistent behavior to other MFC classes.

A second good reason for having the caller call Create is that from a constructor you have limited means of reporting any errors. You can just throw an exception, whereas in a separate Create function you can return a value.