Parent topic: Style attributes reference
Presentation styles / Style attributes reference

Window style attributes

Window style presentation attributes apply to a window.

Table 1. Window style attributes
Attribute Description GDC CLIENT HTML5 CLIENT
actionPanelButtonSize

Defines the width of buttons. Values can be "normal", "shrink", "tiny", "small", "medium", "large" or "huge". When using "normal" and "shrink", buttons are sized according to the text or image, where "shrink" uses the minimum size needed to display the content of the button.

Default is "normal".

 Yes No
actionPanelButtonSpace

Defines the space between buttons. Values can be "none", "tiny", "small", "medium", "large" or "huge".

Default is "medium".

 Yes No
actionPanelButtonTextAlign

Defines the text alignment inside buttons. Values can be "left", "center", "right".

Default is "left" when the button have an icon, "center" otherwise.

 Yes Yes
actionPanelButtonTextHidden

Defines the text visibility inside buttons. Values can be "yes" or "no".

Default is "yes".

 Yes Yes
actionPanelDecoration

Defines the decoration of the action panel. Values can be "auto", "yes", "no" and "dockable".

Default is "auto".

 Yes No
actionPanelHAlign

Defines the alignment of the action panel when actionPanelPosition is "top" or "bottom".

Values can be "left", "right" or "center".

Default is "left".

 Yes No
actionPanelPosition

Defines the position of the action button frame (OK/Cancel). Values can be "none", "top", "left", "bottom" or "right".

Default is "right".

 Yes Yes
actionPanelScroll Defines if the action panel is "ring" - that is, when the last button is shown, pressing on the "down" button will show the first one again. Values can be "0" or "1". Default is "1". Yes No
actionPanelScrollStep

Defines how the action panel should scroll when clicking the "down" button, to shown the next visible buttons.

Values can be:
  • "line" (default): the panel will scroll by one line, and then show only the next button.
  • "page": the scrolling will be done page by page.
 Yes No
border

Defines the border type of the window.

Values can be:
  • "normal" (default): the border is standard, with a normal window header with a caption.
  • "frame": only a frame appears, typically without a window header.
  • "tool": a small window header is used.
  • "none": the window gets no border.
On Linux™ KDE 3.x client machines, any application that is started on the Genero Desktop Client with window style attribute "border" set to "tool" seems to disappear when you click elsewhere than on the window itself. But you can make it appear again by clicking on the GDC console. KDE also allows to configure this behavior: Press Alt-F3, then "Configure Window Behavior" => "Advanced" =br On Mac platforms, using "tool" is not effective.		 Yes No
commentPosition

Defines the rendering for field comments.

Values can be:
  • "statusbar" (default): displays the comment in the window status bar.
  • "popup" will bring a window popup to the front; to be used with care, as it can annoy the end user.
  • "statustip" will add a small "down" arrow button that will show the popup once the user clicks on it; useful to display very long text.
  • "both" will display the comment text in a popup window and then in the status bar.
 Yes No
errorMessagePosition

Defines the rendering of program errors displayed with the ERROR instruction.

Values can be:
  • "statusbar" (default): displays the comment in the window status bar.
  • "popup" will bring a window popup to the front; to be used with care, as it can annoy the end user.
  • "statustip" will add a small "down" arrow button that will show the popup once the user clicks on it; useful to display very long text.
  • "both" will display the comment text in a popup window and then in the status bar.
 Yes No
forceDefaultSettings

Indicates if the window content must be initialized with the saved positions and sizes. By default, windows are reopened at the position and with the size they had when they were closed. You can force the use of the initial settings with this attribute. This applies also to column position and width in tables.

Default is "0".

 Yes No
formScroll

Defines if scrollbars should always be displayed when the form is bigger than screen, or only when the window is maximized.

Values can be "yes" or "no".

Default is "yes".

 Yes No
ignoreMinimizeSetting

Defines if the stored settings "state=minimize" must be ignored when loading settings.

To be used when minimized windows should not be shown minimized again when reopen.

Values can be "yes" or "no".

Default is "no".

 Yes No
menuPopupPosition

Defines the position of the automatic menu for "popup" menus.

Values can be:
  • "cursor" (default) - the popup menu appears at the cursor position.
  • "field" - the popup menu appears below the current field.
  • "center" - the popup menu appears at the center of the screen.
  • "center2" - the popup menu appears at the center of the current window.
 Yes No
messagePosition

Defines the rendering for program messages displayed with the MESSAGE instruction.

Values can be:
  • "statusbar" (default): displays the comment in the window status bar.
  • "popup" will bring a window popup to the front; to be used with care, as it can annoy the end user.
  • "statustip" will add a small "down" arrow button that will show the popup once the user clicks on it; useful to display very long text.
  • "both" will display the comment text in a popup window and then in the status bar.
 Yes No
position

Indicates the initial position of the window.

Values can be:
  • "default" (default): the windows are displayed according to the window manager rules.
  • "field": the window is displayed below the current field (works as "default", when current field does not exist).
  • "previous" the window is displayed at the same position (top left corner) as the previous window. (works as "default" when there is no previous window).
  • "center": the window is displayed in the center of the screen.
  • "center2": the window is displayed in the center of the current window.

For front-ends using stored settings, "field", "previous" and "previous" have higher priority than the settings.

 Yes No
ringMenuButtonSize

Defines the width of buttons.

Values can be "normal", "shrink", "tiny", "small", "medium", "large" or "huge".

When using "normal" and "shrink", buttons are sized according to the text or image, where "shrink" uses the minimum size needed to display the content of the button.

Default is "normal".

 Yes No
ringMenuButtonSpace

Defines the space between buttons.

Values can be "none", "tiny", "small", "medium", "large" or "huge".

Default is "medium".

 Yes No
ringMenuButtonTextAlign

Defines the text alignment inside buttons.

Values can be "left", "center", "right"

Default is "left" when the button have an icon, "center" otherwise.

 Yes Yes
ringMenuButtonTextHidden

Defines the text visibility inside buttons.

Values can be "yes" or "no". Default is "yes".

 Yes Yes
ringMenuDecoration

Defines the decoration of the menu panel.

Values can be "auto", "yes", "no" and "dockable".

Default is "auto".

 Yes No
ringMenuHAlign

Defines the alignment of the ring menu when ringMenuPosition is "top" or "bottom".

Values can be "left", "right" or "center".

Default is "left".

 Yes No
ringMenuPosition

Defines the position of the ring menu frame for a MENU instruction.

Values can be "none", "top", "left", "bottom" or "right".

Default is "right".

 Yes Yes
ringMenuScroll

Defines if the focus can wrap in the ring menu default actions when pressing up or down keys.

Values can be "0" or "1".

Default is "1".

 Yes No
ringMenuScrollStep

Defines how the ring menu must scroll when moving to a next button that is not visible.

Values can be:
  • "line" (default): the menu will scroll by one line, and show only the next button.
  • "page", the scrolling will be done page by page.
 Yes No
sizable

Defines if the window can be resized by the user.

Values can be "yes", "no" or "auto".

With the GDC, when using "auto", the window becomes resizeable if the content of the first displayed form has resizeable elements, for example when using a form with a TABLE container or an TEXTEDIT with STRETCH attribute.

With GWC, the behavior is applied to the form instead of the window. When set to "no", the form content is not stretched even if the form contains stretchable items.

Note: On Linux and Mac platforms, most of window managers don't take into account sizable when it is set to "no".

Default is "yes".

 Yes Yes
startMenuAccelerator

Defines the shortcut keys to execute the selected start menu item, when the position is defined as "tree" or "poptree".

By default, "space", "enter" and "return" start the application linked to the current item.

 Yes No
startMenuExecShortcut2

Defines the shortcut keys to execute the selected start menu item, when the position is defined as "tree" or "poptree".

By default, "space", "enter" and "return" start the application linked to the current item.

 Yes No
startMenuPosition

Indicates the position of the start menu, when one is defined.

Values can be:
  • "none" (default): the startmenu is not displayed.
  • "tree": the start menu is displayed as a treeview, always visible on the right side of the window.
  • "menu": the start menu is displayed as a pull-down menu, always visible at the top of the window.
  • "poptree": the start menu is displayed as a tree view in a popup window that can be opened with a shortcut (see startMenuShortcut).
 Yes If set to "none", the start menu is not displayed. For other settings, always displayed as a tree.
startMenuShortcut

Defines the shortcut key to open a start menu, when the position is defined as "poptree".

Default is "control-shift-F12".

 Yes No
startMenuSize

Defines the size of the start menu, when one is defined and the position is defined as "tree" or "poptree".

Values can be "tiny", "small", "medium", "large" or "huge".

Default is "medium".

Note: The size will also depend on the font used for the startmenu.
 Yes No
statusBarType

Defines the type of status bar the window will display.

See Status bar types for all possible values.

Default is "default".

 Yes No
tabbedContainer

For the GDC, defines if the WCI container must display the child application windows in a folder tab.

For the GWC, this attribute specifies whether child applications are to be displayed inside the same browser window as the parent, or in a new window. WCI is not supported by GWC.

Values can be "no" (default), "yes".

 Yes Yes
tabbedContainerCloseMethod

Defines the folder tab method of the container when tabbedContainer is set to "yes".

Values can be:
  • "container" (default): container gets a close button in the tab.
  • "page": each page has its own close button.
  • "both": each page and the container has its close button.
  • "none": no close button is shown.
 Yes No
thinScrollbarDisplayTime

Defines the display time (in seconds) of the automatic scrollbar displayed when scrolling on fixed screen array (a.k.a. "Matrix") and SCROLLGRIDs. After the delay, the scrollbar will disappear.

Default is 1 second.

 Yes Yes
toolBarDocking

Defines if the toolbar is movable and floatable.

Values can be "yes" (default), "no".

 Yes No
toolBarPosition

Indicates the position of the toolbar, when a toolbar is defined.

Values can be "none", "top", "left", "bottom" or "right".

Default is "top".

 Yes No
windowMenu

Defines if the WCI container should display an automatic "Window" menu, with Cascade and Tile features, and list of child windows.

Values can be "yes", "no" (default).

 Yes No
windowOptionClose

Defines if the window can be closed with a system menu option or window header button.

Values can be "yes", "no" or "auto".

When value is "auto", the option is enabled according to the window type.

Default is "auto".

This attribute may have different behavior depending on the front end operating system. For example, when no system menu is used, it may not be possible to have this option enabled.

 Yes Yes
windowOptionMaximize

Defines if the window can be maximized with a system menu option or window header button.

Values can be "yes", "no" or "auto".

When value is "auto", the option is enabled according to the window type.

Default is "auto".

This attribute may have different behavior depending on the front end operating system. For example, when no system menu is used, it may not be possible to have this option enabled.

 Yes No
windowOptionMinimize

Defines if the window can be minimized with a system menu option or window header button.

Values can be "yes", "no" or "auto".

When value is "auto", the option is enabled according to the window type.

Default is "auto".

This attribute may have different behavior depending on the front end operating system. For example, when no system menu is used, it may not be possible to have this option enabled.

 Yes No
windowState

Defines the initial state of a window.

Values can be "normal", "maximized" or "minimized".

Default is "normal".

 Yes No
windowSystemMenu

Defines if the window shows a system menu.

Values can be "yes", "no" or "auto".

When value is "auto", the system menu is enabled according to the window type.

Default is "auto".

 Yes Only "auto" is supported.
windowType

Defines the basic type of the window.

Values can be:
  • "normal" (default): Normal windows are displayed as typical application windows.
  • "modal": Modal windows are displayed at the top of all other windows, typically used for temporary dialogs.
 Yes Yes
Related concepts
Windows and forms in programs
Parent topic: Style attributes reference