Microsoft Foundation Class Library for Windows CE: ScreenCapture
AppWizard has created this ScreenCapture application for you. This application
not only demonstrates the basics of using the Microsoft Foundation classes
but is also a starting point for writing your application.
This file contains a summary of what you will find in each of the files that
make up your ScreenCapture application.
This is the main header file for the application. It includes other
project specific headers (including Resource.h) and declares the
CScreenCaptureApp application class.
This is the main application source file that contains the application
This is a listing of all of the Microsoft Windows CE 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 Microsoft
eMbedded Visual C++.
This is an icon file, which is used as the application's icon. This
icon is included by the main resource file ScreenCapture.rc.
This file contains resources that are not edited by Microsoft
eMbedded Visual C++. You should place all resources not
editable by the resource editor in this file.
This file contains information used by ClassWizard to edit existing
classes or add new classes. ClassWizard also uses this file to store
information needed to create and edit message maps and dialog data
maps and to create prototype member functions.
AppWizard creates one dialog class:
ScreenCaptureDlg.h, ScreenCaptureDlg.cpp - the dialog
These files contain your CScreenCaptureDlg class. This class defines
the behavior of your application's main dialog. The dialog's
template is in ScreenCapture.rc, which can be edited in Microsoft
Other standard files:
These files are used to build a precompiled header (PCH) file
named ScreenCapture.pch and a precompiled types file named StdAfx.obj.
This is the standard header file, which defines new resource IDs.
Microsoft eMbedded Visual C++ reads and updates this file.
AppWizard uses "TODO:" to indicate parts of the source code you
should add to or customize.
If your application uses MFC in 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 MFCWCXXX.DLL from
the Microsoft eMbedded 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, MFCWCDEU.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.