From WTL to MFC (2) trap the wizard (dialog Chapter)
Description: WTL basic characteristics, and wrote articles in the following.
So, then I would like WTL to create a screen using a simple dialog.
It is written in the title, here, MFC, so you want to describe the differences between, MFC I would describe the difference between Wizard.
For environmental uses of the environment created by the article.
[File]
- [New]
- [Projects]
The following screen appears.

"Project" an appropriate name (in this case, for example "dlgtest" and.
) Set, "OK" button.

"Next" button.

Here,
The left "type of application" in "DAIAROGUBESU" from the menu.
"Modal dialog" is put in check.
The right of the screen "project options" in ". CPP file" is put in check.
(MFC wizards come up with to compare with the CPP CPP file)
"Finish" button.
As an example "dlgtest" If the project name should be created the following files.
| WTL | MFC |
| res / dlgtest.ico
dlgtest.cpp |
res / dlgtest.ico res / dlgtest.manifest res/dlgtest.rc2 dlgtest.cpp dlgtest.h dlgtest.rc dlgtestDlg.cpp dlgtestDlg.h Resource.h stdafx.cpp stdafx.h |
MainDlg (WTL) and dlgtestDlg (MFC), the name is different, the same functional class.
If you have a resource for some of the files is different, almost one to one support files.
(It is not more exaggerated than the trap.... )
Before it, the end of the wizard, "Finish" when you click a button to output the following error, the project may not be loaded automatically.
This is the UIZADOSUKURIPUTO, Express does not occur because it is recognized correctly in the wizard.
WTL UIZADOSETTOAPPU of script files (setupxx.js) as follows: add a line.
※ script file,
- % WTL installation directory% \ AppWiz \ setupxx.js
Our name.
xx setupxx.js of the
- 70:
For VC + +70
71:
For VC + +71
80:
For VC + +80
.
90: VC + +90 for, officially, not yet.
Individually, many are available on the site.
We also offer at this site.
setup90.js below the 124 line and add a line per line.
1 2 3 | fileDest.WriteLine("Param=\"NO_RESOURCE_EDITOR = 1\""); // add following line. fileDest.WriteLine("Param=\"VC_EXPRESS = 1\""); |
Change the above, after saving, double-click, and then set up.
Later in the wizard, the error would not.
When we compile and run it, you'll see a screen similar to the following simple.

You might also like:
Trackback URL
After Admin approves this comment, it will be shown.
Comments
Leave a Reply
