-------------------------------------------------------------------------------- Matrox Imaging Library MDispMFC.txt Readme File November 1, 2003 Copyright © 2003 by Matrox Electronic Systems Ltd. All rights reserved. -------------------------------------------------------------------------------- This document explains the current limitations and particularities when using the AppWizard application (see your MDispMFC example). This application, which is accessed in Visual C++, not only demonstrates the basics of using the Microsoft Foundation classes, but is also a starting point for writing your MIL applications. This document contains a summary of what you will find in each of the files that make up your MDispMFC application. Contents 1. Important Files. 2. For the main frame window. 3. AppWizard: one document type and one view. 4. Other standard files. 5. Other notes. 1. Important Files. - MDispMFC.h: This is the main header file for the application. It includes other project specific headers (including Resource.h) and declares the CMDispMFCApp application class. - MDispMFC.cpp: This is the main application source file that contains the application class CMDispMFCApp. - MDispMFC.rc: This is a listing of all of the Microsoft Windows resources that the program uses. It includes the icons, bitmaps, and cursors that are stored in the RES subdirectory. This file can be directly edited in the Microsoft Developer Studio. - res\MDispMFC.ico: This is an icon file, which is used for the application's icon. This icon is included by the main resource file MDispMFC.rc. - res\MDispMFC.rc2: This file contains resources that are not edited by Microsoft Developer Studio. You should place all resources that can not be edited by the resource editor in this file. - MDispMFC.clw: This file contains information used by ClassWizard to edit existing classes or to add new classes. ClassWizard also uses this file to store information needed to create and edit message maps, dialog data maps and to create prototype member functions. 2. For the main frame window. - MainFrm.h, MainFrm.cpp: These files contain the frame class CMainFrame, which is derived from CMDIFrameWnd, and controls all MDI frame features. - res\Toolbar.bmp: This bitmap file is used to create tiled images for the toolbar. The initial toolbar and status bar are constructed in the CMainFrame class. Edit this toolbar bitmap along with the array in MainFrm.cpp to add more toolbar buttons. 3. AppWizard: one document type and one view. - MDispMFCDoc.h, MDispMFCDoc.cpp (the document): These files contain your CMDispMFCDoc class. Edit these files to add your special document data and to implement file saving and loading (via CMDispMFCDoc::Serialize). - MDispMFCView.h, MDispMFCView.cpp (the view of the document): These files contain your CMDispMFCView class. CMDispMFCView objects are used to view CMDispMFCDoc objects. - res\MDispMFCDoc.ico: This is an icon file that is used for the icon regarding MDI child windows for the CMDispMFCDoc class. This icon is included by the main resource file MDispMFC.rc. 4. Other standard files. - StdAfx.h, StdAfx.cpp: These files are used to build a precompiled header (PCH), with the file name MDispMFC.pch, and precompiled types, with the file named StdAfx.obj. - Resource.h: This is the standard header file that defines new resource IDs. Microsoft Developer Studio reads and updates this file. 5. Other notes. - AppWizard uses "TODO:" to indicate parts of the source code you should add to or customize. - If your application uses MFC for a shared DLL, and your application is in a language other than the operating system's current language, you will need to copy the corresponding localized resources MFC40XXX.DLL from the Microsoft Visual C++ CD-ROM onto the system or system32 directory, and rename it to be MFCLOC.DLL. ("XXX" stands for the language abbreviation. For example, MFC40DEU.DLL contains resources translated to German.) If you don't do this, some of the UI elements of your application will remain in the language of the operating system.