Adding Controls to a Dialog Causes the Dialog to No Longer Function
The latest version of this topic can be found at Adding Controls to a Dialog Causes the Dialog to No Longer Function.
After adding a common control or rich edit control to a dialog box, it will not appear when you test the dialog box or the dialog itself will not appear.
Example of the problem
Create a Win32 project, modifying the application settings so you create a Windows application (not a console app).
In Resource View, double click on the .rc file.
Under the dialog option, double click the About box.
Add an IP Address Control to the dialog box.
Save and Rebuild all.
Execute the program.
On the dialog box's Help menu, click the About command; no dialog box is displayed.
The cause
Currently, the Dialog editor does not automatically add code to your project when you drag and drop the following common controls or rich edit controls onto a dialog box. Nor does Visual Studio provide an error or warning when this problem occurs. You must add the code for the control manually.
| Slider Control | Tree Control | Date Time Picker |
| Spin Control | Tab Control | Month Calendar |
| Progress Control | Animation Control | IP Address Control |
| Hot Key | Rich Edit Control | Extended Combo Box |
| List Control | Rich Edit 2.0 Control | Custom Control |
The fix for common controls
In order to use common controls on a dialog box, you need to call InitCommonControlsEx or AFXInitCommonControls before you create the dialog box.
The fix for RichEdit controls
You must call LoadLibrary for rich edit controls. For more information, see Using the RichEdit 1.0 Control with MFC, About Rich Edit Controls in the Windows SDK, and Overview of the Rich Edit Control.
Requirements
Win32