Switch between 2 dialogs - MFC

Question

0.00/5 (No votes)

See more:

Yeah, but even though i removed PreTranslateMessage(MSG* pMsg) function about the second dialog, it still continued showing me that error:

Debug Assertion Failed: wincore.cpp line 875

The code in wincore.cpp says:

void CWnd::OnFinalRelease()
{
if (m_hWnd != NULL)
DestroyWindow(); // will call PostNcDestroy
else
PostNcDestroy();
}

Posted 26-Feb-10 7:25am

George Findulov

Updated 26-Feb-10 8:48am

v3

Add a Solution

1 solution

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)

Avi Berger · Answer 1 · 2010-02-26T08:13:00

I don't see why you are fiddling with PreTranslateMessage() for your second dialog. The escape key should activate the OnCancel() of your second dialog. The one provided in CDialog should close the dialog.

Edit:

Well, one item eliminated though it wasn't the problem. I have several thoughts/suggestions. I don't know if any will be helpful.

1) A dialog box without any controls on it is decidedly odd. I don't know why you want such a thing. I also don't know how microsoft's code will or won't deal with such a thing. Try adding a control that can accept focus ( a push button will do) to your dialog even though you don't have it doing anything. Does it make a difference?

2) Can you use the debugger & check/confirm which window/dialog is triggering the assertion?

3) You are not showing the actual assertion that failed. What is it? It should be on the referenced line in the source code.

4) How are you handling closing your main (first) dialog?