what is '1000 projects'?

how it works?

more number of projects?

Download The VC++ Engineering Project

Title: memory game

Title: memory game Title: KBC Description: How to developing GUI or graphics programming in VC++ and using sound in VC++ AppWizard has created this v 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 v application. v.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. v.h This is the main header file for the application. It includes other project specific headers (including Resource.h) and declares the CVApp application class. v.cpp This is the main application source file that contains the application class CVApp. v.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++. v.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\v.ico This is an icon file, which is used as the application's icon. This icon is included by the main resource file v.rc. res\v.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. Documentation for the CMUgraphics package is found in Manual.txt. Release notes for Version 1.2 of the package -------------------------------------------- Due to some name conflicts, graphics.h has been renamed to CMUgraphics.h (and graphics.cpp, CMUgraphics.cpp) Some constants have been renamed (from version 1.1): L_CLICK -> LEFT_CLICK R_CLICK -> RIGHT_CLICK LEFT -> LEFT_BUTTON RIGHT -> RIGHT_BUTTON Also, the default destructor behavior of the window object has changed. If a window is the last window object on screen, it will now not disappear until the mouse has been clicked in the window. This behavior can be changed using the SetWaitClose function described in "Manual.txt". With this release, the source for each compiler is the same; compiler differences are resolved in the file version.h. An example of the use of this file is if you're using Metrowerks version 3, you need to uncomment the following #define #define __MW_CODEWARRIOR3__ and comment out this one #define __MW_CODEWARRIOR4__ Some other notes on using the package follow: --------------------------------------- Demo.cpp is included in the source code for the project and exercises virtually all of the member functions in the CMUgraphics package. Also included in the graphics folder is House.cpp which is more emblematic of a first assignment's solution. In Metrowerks CodeWarrior, to compile House.cpp instead of Demo.cpp, drag it into the project window and remove Demo.cpp from the project. In Microsoft Visual C++, remove Demo.cpp from the project and then go to the Project menu and select the "Add to Project" submenu and finally select files. Then use the standard file dialog to locate and add House.cpp. In Borland, drag House.cpp into the project window and remove Demo.cpp from the project. ----------------------------- The demo makes use of an ostringstream which is fairly new to the C++ Standard and supersedes the older ostrstream. If your compiler does not support ostringstreams, e.g., it complains about the #include statement or the declaration of the ostringstream, you should do the following: replace #include with #include and replace every declaration of output (there are five) ostringstream output; with ostrstream output; --------------------------------- Notes for Borland users: the library and include paths are currently set to c:\bc5\lib and c:\bc5\include. If your standard libraries are located in a different directory, you will have to right-click the top-level project node, select Edit Local Options and change the paths appropriately. Once you compile the project, you'll notice many warnings are generated. All can be safely ignored; if you figure out how to suppress them, download project