BUTTON control styles

%BS_AUTO3STATE

The control is a 3-state checkbox control that automatically updates itself when clicked/toggled. Do not use with the %BS_DEFAULT or %BS_DEFPUSHBUTTON styles.

%BS_AUTOCHECKBOX 

The control is a checkbox control that automatically updates itself when clicked/toggled.

%BS_BOTTOM

Place the text at the bottom edge of the button.

%BS_CENTER

Center the text horizontally in the button. (default)

%BS_DEFAULT

Create a button with a heavy black border. The user can select this button by pressing the ENTER key. This style is useful for enabling the user to quickly select the most likely option. You can only have one Default button per dialog. It is recommended to make id& = 1, or id& = %IDOK for this control. Synonym of %BS_DEFPUSHBUTTON.

%BS_FLAT 

Create a flat button (without the raised 3D look).

%BS_LEFT

Place the text against the left side of the button.

%BS_MULTILINE

Wrap the caption text across multiple lines, if the text string is too long to fit on a single line in the button. To force a wrap, insert a $CR (or $CRLF) into the caption text at the desired wrap position.

%BS_NOTIFY

Enable a button to send the %BN_KILLFOCUS and %BN_SETFOCUS notification messages to the button Callback Function.

%BS_OWNERDRAW

The parent dialog Callback Function receives %WM_DRAWITEM messages when the control needs to be redrawn due to state changes or normal repainting.

%BS_PUSHBUTTON

The control is a push button control which sends %WM_COMMAND messages to the Callback Function of the parent dialog. (default)

%BS_PUSHLIKE

Button state alternates (toggles) between normal (raised) and depressed (sunken) modes.

%BS_RIGHT

Place the text on the right side of the button.

%BS_TEXT

Control displays a text caption/title. (default)

%BS_TOP

Place the text at the top edge of the button.

%BS_VCENTER

Center the text vertically in the button. (default)

%WS_BORDER

Add a thin line border around the control.

%WS_DISABLED

Create a control that is initially disabled. A disabled control cannot receive input from the user. Use the CONTROL ENABLE statement to re-enable the button.

%WS_GROUP

Define the start of a group of controls. The first control in each group should also use %WS_TABSTOP style. The next %WS_GROUP control in the tab order defines the end of this group and the start of a new group. Groups configured this way permit the arrow keys to shift focus between the controls within the group, and focus can jump from group to group with the usual TAB and SHIFT+TAB keys. Both tab stops and groups are permitted to wrap from the end of the tab order back to the start.

%WS_TABSTOP

Allow button control to receive keyboard focus when the user presses the TAB and SHIFT+TAB keys. The TAB key shifts keyboard focus to the next control with the %WS_TABSTOP style, and SHIFT+TAB shifts focus to the previous control with %WS_TABSTOP. (default)

%WS_EX_ACCEPTFILES

The control will accept Drag+Drop files.

%WS_EX_CLIENTEDGE

Apply a sunken edge border to the control.

%WS_EX_DLGMODALFRAME

The control has a double border.

%WS_EX_LEFT

The control has generic "left-aligned" properties. (default)

%WS_EX_LTRREADING

Display the caption text using Left to Right reading-order properties. (default)

%WS_EX_RIGHT

The control has generic "right-aligned" properties. This style has an effect only if the shell language is Hebrew, Arabic, or another language that supports reading order alignment; otherwise, the style is ignored.

%WS_EX_RTLREADING

If the shell language is Hebrew, Arabic, or another language that supports reading order alignment, the caption text is displayed using Right to Left reading-order properties. For other languages, the style is ignored.

%WS_EX_STATICEDGE

Apply a three-dimensional border style to the control (intended to be used for items that do not accept user input).

%WS_EX_TRANSPARENT 

Controls/windows beneath the dialog are drawn before the dialog is drawn. The dialog is deemed transparent because elements behind the dialog have already been painted - the dialog itself is not drawn differently. True transparency is achieved by using Regions - see MSDN and/or the Platform SDK documentation for more information.