OnInitDialog does not work MFC

Question

0.00/5 (No votes)

See more:

Hello all,

in my Appliation I have 2 Dialogs : DialA and DialB

In The DialB::OnInitDialog() I Have some parameters intialization like SetLimitText etc ...

When I call DialB via DialA (by pressing a buttom) the preparameters set on the DialB::OninitDialog() does work. But when i Call DialB from The Menu All works fine.

i even trie to go step by step via debug mode but the prog don't go the breakpoints when i Call DialB via DialA.

What is Wrong ? I need that the DilB:OnInitDialog Works for both. Help Plz

Code of CDialB (copied from OP non-solution)

C++

BOOL CDialB::OnInitDialog()
{
    CDialog::OnInitDialog();
    m_Edit_TRIMESTRECTR.SetLimitText(3);
    UpdateData(TRUE);
 
    return TRUE;  // return TRUE unless you set the focus to a control
    // EXCEPTION: OCX Property Pages should return FALSE
}

Posted 21-Dec-12 2:59am

Schehaider_Aymen

Updated 21-Dec-12 5:51am

André Kraak

v4

Add a Solution

Comments

Jochen Arndt 21-Dec-12 9:11am

You should show us the code portion from DialA where you create and show the DialB dialog.

Schehaider_Aymen 21-Dec-12 9:27am

See answer 1 for my code

Jochen Arndt 21-Dec-12 9:32am

NO!

Use the green 'Improve question' link to edit your question and add additional information like code snippets. Afterwards, delete the solution.

[no name] 22-Dec-12 1:40am

You should provide some additional information. Otherwise we can't detect the problem

Mohibur Rashid 22-Dec-12 2:17am

I don't even call CDialog::OnInitDialog(); in my function but that is not the problem.

Now, Make sure you have done your CDialB() construction properly. with proper id.

ranjithkumar81 26-Dec-12 4:38am

Have you created modal dialog or modless dialog?
paste the pice of code here.

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)

Michael Haephrati · Answer 1 · 2013-03-07T10:50:00

Solution 2

OnInitDialog() is only called once, so if it was already called, it will not be called again. There are better ways to do something every time a dialog is displayed or opened.

Posted 7-Mar-13 10:50am

Michael Haephrati

Albert Holguin · Answer 2 · 2013-03-07T16:13:00

OnInitDialog() is only called when the dialog is first created and meant to load default values of GUI components (and anything else you need to do AFTER the dialog components have been created but BEFORE the regular operation of the dialog).... with that said, if you need to set something EVERY time you bring up the dialog.

CEdit::SetLimitText() only needs to be called once during the existance of a dialog and the CEdit control, therefore it is appropriate that it's called in the method OnInitDialog(), however, there really should be no reason for you to continually set it.

When you make a CDialog you can do it in two ways, make it once at the beginning of the application execution and just bring it up when you need it (appropriate for something you'll constantly use) or you can just make it and delete it every time you're going to use it (appropriate when memory usage is at a premium, but heap allocations can be relatively slow so keep that in mind). The simple way is to just make the dialog off the back and bring it up when you need it, in that case, OnInitDialog() will only be called once during the entire app execution.