Microsoft KB Archive/170511
Article ID: 170511
Article Last Modified on 12/8/2003
- 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 Q170511
You may experience significantly slow performance when using the dialog editor in Visual C++ 5.0 if the projects you are using have several complex dialog boxes that use many controls. You might experience this slowness when you change from one control to another, when you start the Class Wizard, or when you access the properties of a control.
Complex queries need to update the WizardBar while the Dialog Editor is running, and this slows performance.
You can work around this problem by disabling the Wizard Bar as follows:
- On the Tools menu, select Customize.
- In the Customize dialog box, select the Toolbars tab.
- In the Toolbars list, scroll to the Wizard Bar check box and de-select it.
- Shut down Developer Studio and restart.
NOTE: The Wizard Bar will not be disabled until you shut down Developer Studio.
This should help resolve the main symptoms.
Double-clicking a control in the Resource Editor will re-invoke hidden WizardBar functionality (the WizardBar will not be displayed). To stop this behavior:
- Always use Ctrl+Tab to toggle between two windows. -or-
- Disable the "Double-click in dialog editor edits code (MFC only)" option. To do this, on the Tools menu, select Options, select the Compatibility tab, and then de-select the "Double-click in dialog editor edits code (MFC only)" check box.
Finally, deleting or renaming the .CLW (Class Wizard) file may provide some relief. The .CLW file is located in the same directory as your project's files (.DSW and .DSP). It is possible to use a batch file that can be called from a toolbar button that is designed to do this. If you do this, a new CLW file will be generated every time you use the Class Wizard.
Microsoft has confirmed this to be a bug in Microsoft Visual C++ 5.0. This problem has been addressed in Visual C++ 6.0 with some performance gains.
Keywords: kbbug kbfix kbprb kbwizard KB170511