MICROSOFT FOUNDATION CLASS LIBRARY : VTHtmlThumbnail
AppWizard has created this VTHtmlThumbnail 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 VTHtmlThumbnail application.
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.
This is the main header file for the application. It includes other
project specific headers (including Resource.h) and declares the
CVTHtmlThumbnailApp application class.
This is the main application source file that contains the application
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
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.
This is an icon file, which is used as the application's icon. This
icon is included by the main resource file VTHtmlThumbnail.rc.
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:
VTHtmlThumbnailDlg.h, VTHtmlThumbnailDlg.cpp - the dialog
These files contain your CVTHtmlThumbnailDlg class. This class defines
the behavior of your application's main dialog. The dialog's
template is in VTHtmlThumbnail.rc, which can be edited in Microsoft
Other standard files:
These files are used to build a precompiled header (PCH) file
named VTHtmlThumbnail.pch and a precompiled types file named StdAfx.obj.
This is the standard header file, which defines new resource IDs.
Microsoft 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 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.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.
I've been programming for 35 years - started in machine language on the National Semiconductor SC/MP chip, moved via the 8080 to the Z80 - graduated through HP Rocky Mountain Basic and HPL - then to C and C++ and now C#.
I used (30 or so years ago when I worked for Hewlett Packard) to repair HP Oscilloscopes and Spectrum Analysers - for a while there I was the one repairing DC to daylight SpecAns in the Asia Pacific area.
Afterward I was the fourth team member added to the Australia Post EPOS project at Unisys Australia. We grew to become an A$400 million project. I wrote a few device drivers for the project under Microsoft OS/2 v 1.3 - did hardware qualification and was part of the rollout team dealing directly with the customer.
Born and bred in Melbourne Australia, now living in Scottsdale Arizona USA, became a US Citizen on September 29th, 2006.
I work for a medical insurance broker, learning how to create ASP.NET websites in VB.Net and C#. It's all good.
Oh, I'm also a Kentucky Colonel. http://www.kycolonels.org
C/C++ Programmer. OS of choice is any Win32 OS. Started working in the gaming industry, programming mainframe VOS OS and dealing with Slot machine serials comms protocols, creating test-tools and line monitoring software on W2K.
Moved on to working in a small software company that worked with electronic forms. Glad I spent most of my time there learning new technologies and increasing my programming skills. I wasn't going to learning anything from anyone there. Well, except the odd one person who is now a CPian.
Now working in a company that works with Security, Identity and Trust Solutions. Learning lots about encryption, signing, digital signatures, hashing and all sorts of new buzz words. It might as well be another language.