Home > Articles

Documents and Views

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

In this chapter

The Document/View architecture is used, with minimal overhead, to provide applications a way to separate data from visualizations of that data in one or more windows.

This is one of the least understood aspects of the Visual Studio framework and often the cause of much debate. Used correctly, however, the Document/View architecture provides a lot of functionality and future expandability to an application.

In this chapter, you will find some practical guides to using this framework effectively, as well as a description of it.

  • "MFC Under the Hood: Creating an MFC Application" provides a feet-first approach to building Document/View applications from the ground up, with some quick information about what's going on.

  • "Using Better Tracing to Understand the Doc/View Architecture" gives those wishing to get an in-depth understanding of the structure of the Document/View architecture a clear picture of what makes it tick.

  • "Command Routing Beyond a Split Frame" describes a simple technique to enable inactive views to process commands.

  • "Replacing a View in a Doc-View Application" is an extremely useful article I find myself referring to on a regular basis. The article describes how to seamlessly swap between various view types at runtime.

MFC Under the Hood: Creating an MFC Application

This article was contributed by Andrew Fenster.

Environment: Visual C++

Most of the time when you are creating a new MFC application, you'll start with the MFC App Wizard. The App Wizard generates a basic skeleton application, which you will flesh out into a full-fledged, useful program.

Even the skeleton application you get from the App Wizard contains a lot of very arcane-looking code, and there's a great deal of hidden code as well. The purpose of this article is to demystify some of that code. I'll show you how to build a simple MFC application without the App Wizard. By the time you are done, the mysterious-looking code that comes from the App Wizard will no longer be so mysterious, and you'll be better prepared to modify it to suit your own purposes.

The Hidden Code First

Every 32-bit Windows application has two essential program elements: WinMain and WndProc. Your program will have one WinMain for the entire program and one WndProc for each window in the program. Although MFC creates these for you, you still need to know a little about them.

WinMain is the function that starts your application. Once your application is running, the Windows operating system will start placing your application's messages in a message queue. WinMain makes three Windows API calls to get these messages from the operating system and to process them. First, it calls GetMessage to retrieve a message. Then, it calls TranslateMessage to perform any necessary conversion of the message. Finally, WinMain calls DispatchMessage, which tells the operating system to send the message to the appropriate WndProc for handling.

Once WndProc receives a message, it looks through its message handlers for instructions on what should be done with the message. Your job as a Windows application programmer is to write the handlers.

A Simple MFC Application: Less than 20 Lines of Code

Next, we'll look at a simple, bare-bones MFC application. MFC provides WinMain and WndProc. We must provide an MFC-derived application class and window management class.

Our application class will be derived from the MFC class CWinApp. CWinApp provides all the member variables and functions to initialize, start, run, and close an application. CWinApp contains a pointer called m_pMainWnd, which will point to an object of our derived window management class. Each MFC application has one and only one object derived directly from CWinApp. In the example below, that class is called "CMyApp."

Our window management class will be derived from CFrameWnd. CFrameWnd has all the member variables and functions to create and manage windows. Note that when you create an object of our derived windows class, you have not created an actual window. The new object uses its Create() function to create windows.

Here's what happens when we start our program. You can follow along in the code:

  1. WinMain runs this code: CMyApp app;. This creates an object of type CMyApp named "app". app will have all the member variables and functions of CWinApp that are needed to start, run, and close our application.

  2. Then WinMain calls app's InitInstance() function. InitInstance() creates a new CMyWnd object with m_pMainWnd = new CMyWnd;.

  3. The CMyWnd constructor calls its Create() function, which creates an instance of the window but does not display it.

  4. The app's InitInstance() function then displays the window with m_pMainWnd-> ShowWindow(m_nCmdShow);.

  5. WinMain calls the app's Run() function, which dispatches messages to the rest of the application.

Here is the code. Try it—it works!

   #include <afxwin.h>

   //derive my own window class from CFrameWnd
   class CMyWin: public CFrameWnd
   {
     public:
     CMyWin( );
     DECLARE_MESSAGE_MAP( )
   };

   //define my window class' constructor:
   CMyWin::CMyWin( )
   {
     Create(0, "This Text Will Appear in the Title Bar");
   }

   //derive my own application class from CWinApp
   class CMyApp: public CWinApp
   {
     public:
     virtual BOOL InitInstance( );
   };

   //define my application class' InitInstance( )
   BOOL CMyApp::InitInstance( )
   {
     m_pMainWnd = new CMyWin( );
     m_pMainWnd->ShowWindow(m_nCmdShow);
     m_pMainWnd->UpdateWindow();
     return TRUE;
   }

   //here is my application's message map
   BEGIN_MESSAGE_MAP(CMyWin, CFrameWnd)
     // any messages to be processed by
     // CMyWin get listed here.
   END_MESSAGE_MAP( )

   //declare an instance of application
   //class for WinMain to use.
   CMyApp app;

Figure 3.1 shows what you get when you compile and run.

Figure 3.1Figure 3.1

Your actual window will be bigger.

Single Document Interface Applications

The code from the preceding section creates a simple, bare-bones application. The code that you will find in a single document interface application is more complicated, but it still works along the same lines. You still have an application class derived from CWinApp. You still have a window management class derived from CFrameWnd. In this case, however, the derived window management class is called CMainFrame.

Your derived application class still has an InitInstance() function, but the function looks a lot more complicated. Among other things, it contains something like this:

   CSingleDocTemplate* pDocTemplate;
   pDocTemplate = new CSingleDocTemplate(
     IDR_MAINFRAME,
     RUNTIME_CLASS(CMyDoc),
     RUNTIME_CLASS(CMainFrame), // main SDI frame window
     RUNTIME_CLASS(CMyView));
   AddDocTemplate(pDocTemplate);

Here, the application object creates a single document template pointer and points it to a new single document template object. There are four parameters passed to the CSingleDocTemplate constructor. The first is an integer, the resource ID for the IDR_MAINFRAME resource. The next three parameters pass class information for my Document class, Frame class, and View class. Then the pointer to this new CSingleDocTemplate is added to the list of document templates maintained by the application object. (In an SDI application, there's only one template.)

IDR_MAINFRAME is a resource containing

  1. The application's icon

  2. The application's menu

  3. The accelerator table that goes with the menu

  4. A document string

The document string contains up to seven pieces of information in substrings separated by "\n" characters:

  1. The title that appears in the frame window's title bar.

  2. The title assigned to new documents. If omitted, the default is "Untitled."

  3. A description of the document type in an MDI application. This substring isn't used in an SDI application.

  4. A description of the document type, followed by its default file name extension, for example, "My Big Program(*.mbp)."

  5. The three letter extension for the document type, for example, ".mbp."

  6. A name with no spaces that identifies the document type in the registry.

  7. A descriptive name of the document type, for example, "My Big Program Document."

Here's a sample string:

"My Big Program\n\n\nMy Big Program(*.mbp)\n.mbp\
   nBigProgram\nMBP Document."

Conclusion

So there you have it. Now that you know a little more about what your wizard- generated code is doing, you can go in and start modifying it. For example, if you want to change the size and positioning of your application's main window, you can modify the Create() function. Try substituting the following code for the Create() function listed in the previous example. You'll get a much smaller window positioned in the upper left corner of the screen.

  RECT x;
  x.top = 30;
  x.left = 30;
  x.bottom = 300;
  x.right = 300;
  Create(NULL, "My New Window", WS_OVERLAPPEDWINDOW, x);

There are a lot of settings and functions you can play with. You might be the type who never changes the default code. Even so, the more you know about what's going on, the better your programs will be.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020