Using the CEdit Control (Drag-and-Drop)

Environment: CEdit Controls

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 DragEdit1 application.

File Name Description
DragEdit1.dsp This file (the project file) contains information at the project level and is used to build a single project or subproject. Other users can share the project (.dsp) file, but they should export the makefiles locally.
DragEdit1.h This is the main header file for the application. It includes other project-specific headers (including Resource.h) and declares the CDragEdit1App application class.
DragEdit1.cpp This is the main application source file that contains the application class CDragEdit1App.
DragEdit1.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 Microsoft Visual C++.
DragEdit1.clw 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.
res\DragEdit1.ico This is an icon file, which is used as the application's icon. This icon is included by the main resource file DragEdit1.rc.
res\DragEdit1.rc2 This file contains resources that are not edited by Microsoft Visual C++. You should place all resources not editable by the resource editor in this file.

AppWizard creates one dialog class:

File Name Description
DragEdit1Dlg.h, DragEdit1Dlg.cpp—the dialog These files contain your CDragEdit1Dlg class. This class defines the behavior of your application's main dialog. The dialog's template is in DragEdit1.rc, which can be edited in Microsoft Visual C++.

Other standard files that are created include:

File Name Description
StdAfx.h, StdAfx.cpp These files are used to build a precompiled header (PCH) file named DragEdit1.pch and a precompiled types file named StdAfx.obj.
Resource.h This is the standard header file, which defines new resource IDs. Microsoft Visual C++ reads and updates this file.

Other Notes

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 MFC42XXX.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, MFC42DEU.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.

Downloads

Download demo project - 9 Kb
Download source - 41 Kb


Comments

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • This paper introduces IBM Java on the IBM PowerLinux 7R2 server and describes IBM's implementation of the Java platform, which includes IBM's Java Virtual Machine and development toolkit.

  • As mobile devices have pushed their way into the enterprise, they have brought cloud apps along with them. This app explosion means account passwords are multiplying, which exposes corporate data and leads to help desk calls from frustrated users. This paper will discover how IT can improve user productivity, gain visibility and control over SaaS and mobile apps, and stop password sprawl. Download this white paper to learn: How you can leverage your existing AD to manage app access. Key capabilities to …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds