MDI app cannot handle ID_FILE_MRU_FILEn message in CMainFrame class?

Question

0.00/5 (No votes)

See more:

Is it normal behavior for the ID_FILE_MRU_FILEn messages to be handled in the document class (where they seem to work fine), but not the CMainFrame class (where they do not work - at least in my app)?

Posted 10-Feb-11 6:21am

Member 2584474

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)

Roger Allen · Answer 1 · 2011-02-15T02:33:00

A quick search of the MFC codebase with ID_FILE_MRU shows that these messages are handled by the CWinApp class.

This maps the command range of ID_FILE_MRU_FILE1..16 to the same function OnOpenRecentFile.

It appears to be teh document object that handles the command because the application object just sends the file to the DocTemplate list, finds the template which can handle the document type (if any) and tries to open it.

The mainframe is never involved in any of these steps.

So I am not too sure what your problem is, can you add any additional details?