PRB: Dialog Editor Does Not Retain Unsupported Styles

ID: Q74264

The information in this article applies to:

Microsoft Windows Software Development Kit for Windows versions 3.1 and 3.0
Microsoft Win32 SDK, versions 3.5, 3.51, and 4.0

SYMPTOMS

The Windows Dialog Editor does not retain control/dialog styles that it does not support.

RESOLUTION

The styles in question must be manually added to the dialog script before using the resource compiler to compile the resource script.

MORE INFORMATION

Any style that cannot be explicitly set in the Dialog Editor Styles dialog box will not be present in the script file generated by the the Dialog Editor. For example, the edit control style, ES_OEMCONVERT is not available in the Dialog Editor Styles dialog box. If this style is manually added to the dialog script, compiled, and then loaded into the Dialog Editor, the ES_OEMCONVERT style will be removed.

Any styles that are not supported by the Dialog Editor must be manually added to the dialog script. To modify the dialog script, use a text editor to combine the desired styles using the bitwise OR operator("|"). This modified script should then be included into the application's resource script. If the application's .RES file is later loaded into the Dialog Editor, the unsupported styles will be removed and will need to be added again as described above.

The following is a list of styles that are known not to be supported by the Dialog Editor:

Style


CBS_OEMCONVERT
ES_OEMCONVERT
SBS_BOTTOMALIGN
SBS_LEFTALIGN
SBS_RIGHTALIGN
SBS_SIZEBOX
SBS_SIZEBOXBOTTOMRIGHTALIGN
SBS_SIZEBOXTOPLEFTALIGN
SBS_TOPALIGN
SS_LEFTNOWORDWRAP
SS_NOPREFIX
SS_USERITEM

In addition to the above control styles, any menu definitions added to the dialog script via the MENU resource statement will be deleted by the Dialog Editor.

Additional query words: 3.00 3.10 3.50 4.00 95 win16sdk


Keywords          : 
Version           : 
Platform          : 
Issue type        :

Last Reviewed: March 4, 1999