PRB: Custom AppWizard Doesn't Initialize Custom Step Dialogs
Article ID: 152255
Article Last Modified on 11/21/2006
APPLIES TO
- Microsoft Foundation Class Library 4.2, when used with:
- Microsoft Visual C++ 4.0 Standard Edition
- Microsoft Visual C++ 4.1 Subscription
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 6.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
- Microsoft Visual C++ 6.0 Professional Edition
- Microsoft Visual C++ 6.0 Standard Edition
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.
Keywords: kbcustomwizard kbpending kbprb kbwizard KB152255