sl@0: ======================================================================== sl@0: MICROSOFT FOUNDATION CLASS LIBRARY : t_usb_win sl@0: ======================================================================== sl@0: sl@0: sl@0: AppWizard has created this t_usb_win application for you. This application sl@0: not only demonstrates the basics of using the Microsoft Foundation classes sl@0: but is also a starting point for writing your application. sl@0: sl@0: This file contains a summary of what you will find in each of the files that sl@0: make up your t_usb_win application. sl@0: sl@0: t_usb_win.dsp sl@0: This file (the project file) contains information at the project level and sl@0: is used to build a single project or subproject. Other users can share the sl@0: project (.dsp) file, but they should export the makefiles locally. sl@0: sl@0: t_usb_win.h sl@0: This is the main header file for the application. It includes other sl@0: project specific headers (including Resource.h) and declares the sl@0: CT_usb_winApp application class. sl@0: sl@0: t_usb_win.cpp sl@0: This is the main application source file that contains the application sl@0: class CT_usb_winApp. sl@0: sl@0: t_usb_win.rc sl@0: This is a listing of all of the Microsoft Windows resources that the sl@0: program uses. It includes the icons, bitmaps, and cursors that are stored sl@0: in the RES subdirectory. This file can be directly edited in Microsoft sl@0: Visual C++. sl@0: sl@0: t_usb_win.clw sl@0: This file contains information used by ClassWizard to edit existing sl@0: classes or add new classes. ClassWizard also uses this file to store sl@0: information needed to create and edit message maps and dialog data sl@0: maps and to create prototype member functions. sl@0: sl@0: res\t_usb_win.ico sl@0: This is an icon file, which is used as the application's icon. This sl@0: icon is included by the main resource file t_usb_win.rc. sl@0: sl@0: res\t_usb_win.rc2 sl@0: This file contains resources that are not edited by Microsoft sl@0: Visual C++. You should place all resources not editable by sl@0: the resource editor in this file. sl@0: sl@0: sl@0: sl@0: sl@0: ///////////////////////////////////////////////////////////////////////////// sl@0: sl@0: AppWizard creates one dialog class: sl@0: sl@0: t_usb_winDlg.h, t_usb_winDlg.cpp - the dialog sl@0: These files contain your CT_usb_winDlg class. This class defines sl@0: the behavior of your application's main dialog. The dialog's sl@0: template is in t_usb_win.rc, which can be edited in Microsoft sl@0: Visual C++. sl@0: sl@0: sl@0: ///////////////////////////////////////////////////////////////////////////// sl@0: Other standard files: sl@0: sl@0: StdAfx.h, StdAfx.cpp sl@0: These files are used to build a precompiled header (PCH) file sl@0: named t_usb_win.pch and a precompiled types file named StdAfx.obj. sl@0: sl@0: Resource.h sl@0: This is the standard header file, which defines new resource IDs. sl@0: Microsoft Visual C++ reads and updates this file. sl@0: sl@0: ///////////////////////////////////////////////////////////////////////////// sl@0: Other notes: sl@0: sl@0: AppWizard uses "TODO:" to indicate parts of the source code you sl@0: should add to or customize. sl@0: sl@0: If your application uses MFC in a shared DLL, and your application is sl@0: in a language other than the operating system's current language, you sl@0: will need to copy the corresponding localized resources MFC42XXX.DLL sl@0: from the Microsoft Visual C++ CD-ROM onto the system or system32 directory, sl@0: and rename it to be MFCLOC.DLL. ("XXX" stands for the language abbreviation. sl@0: For example, MFC42DEU.DLL contains resources translated to German.) If you sl@0: don't do this, some of the UI elements of your application will remain in the sl@0: language of the operating system. sl@0: sl@0: /////////////////////////////////////////////////////////////////////////////