Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I used Visual Studio’s Application Wizard to create a skeleton MFC program with a multi-document interface. When I start this program, it automatically creates a child frame, which I don’t want it to do – I need the main frame’s client area to be empty until the user chooses to open a file.
The debugger tells me that a CChildFrame object is created when the application class’s InitInstance() function calls ProcessShellCommand(), but what is a good entry point for me to override this behaviour?
This worked for me — change
to
in your app’s InitInstance() function.