PRB: Custom AppWizard Doesn't Initialize Custom Step Dialogs (152255)
The information in this article applies to:
- The Microsoft Foundation Classes (MFC), when used with:
- Microsoft Visual C++, 32-bit Editions 4.0
- Microsoft Visual C++, 32-bit Editions 4.1
- Microsoft Visual C++, 32-bit Enterprise Edition 5.0
- Microsoft Visual C++, 32-bit Enterprise Edition 6.0
- Microsoft Visual C++, 32-bit Professional Edition 5.0
- Microsoft Visual C++, 32-bit Professional Edition 6.0
- Microsoft Visual C++, 32-bit Learning Edition 6.0
This article was previously published under Q152255 SYMPTOMS
Custom AppWizards with some custom steps do not pick up initialization
values for the dialog's controls for these steps from the Resource Editor.
For instance, if the custom step's dialog template contains a Combo Box,
the strings for the Combo Box can be entered in the Resource Editor itself.
When the Wizard is built and run, and when the custom step containing the
Combo Box comes up, the strings don't show up in the Combo Box. The same
also happens with a picture control with a bitmap associated with it.
CAUSE
For the custom step dialog boxes, Custom AppWizards ignore any
initialization information setup in the Resource Editor.
RESOLUTION
Each custom step's dialog template has a corresponding CAppWizStepDlg-
derived class. The necessary initialization should be done in this class's
OnInitDialog member function. Because this function is called before the
dialog is visible to the user, the effect is as if the initializations were
done in the Resource Editor.
STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 12/1/2003 |
---|
Keywords: | kbCustomWizard kbpending kbprb kbwizard KB152255 |
---|
|