Window style attributes

Window style presentation attributes apply to a window element.

Note: This topic lists presentation style attributes for a specific class of form element, common presentation style attributes can also be used for this type of element.
Table 1. Window style attributes
Attribute GDC GBC GMA GMI
actionPanelButtonSize

Defines the width of buttons for default action views.

By default, buttons are sized depending on the text and/or image.

This attribute gets a size specification as follows:
  • <number>em: a number followed by the "em" unit (such as "20em"), defines a size relative to the height of the current font.
  • "normal", "shrink", "tiny", "small", "medium", "large" or "huge". When using "normal" and "shrink", buttons are sized depending on the text or image, where "shrink" uses the minimum size needed to display the content of the button.
 Yes Yes No No
actionPanelButtonSpace

Defines the space between buttons for default action views.

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

Default is "medium".

 Yes No No No
actionPanelButtonTextAlign

Defines the text alignment inside buttons for default action views.

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

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

 Yes Yes No No
actionPanelButtonTextHidden

Defines the text visibility inside buttons for default action views.

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

 Yes Yes No No
actionPanelDecoration

Defines the decoration of the action panel for default action views.

Values can be "auto" (default), "yes", "no" and "dockable".

 Yes No No No
actionPanelHAlign

Defines the alignment of the action panel for default action views.

This attribute takes effect when actionPanelPosition is "top" or "bottom".

Values can be "left" (default), "right" or "center".

 Yes No No No
actionPanelPosition

Defines the position for default action views frame.

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

 Yes Yes No No
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).

 Yes No No No
actionPanelScrollStep

Defines how the action panel scrolls when clicking the "down" button, and the visibility of the next button.

Values can be:
  • "line" (default): the panel scrolls by one line, and then shows only the next button.
  • "page": the scrolling is done page by page.
 Yes No No No
allowedOrientations

Defines possible orientations for mobile device.

Values can be:
  • "all" (default): Any orientation is allowed.
  • "landscape": Landscape orientation (the display is wider than it is tall).
  • "portrait": Portrait orientation (the display is taller than it is wide).
  • "landscape_reverse": Landscape orientation in the opposite direction from normal landscape.
  • "portrait_reverse": Portrait orientation in the opposite direction from normal portrait.
  • "landscape_all": Normal and reverse landscape orientations are allowed.
  • "portrait_all": Normal and reverse portrait orientation are allowed.
Note: This attribute is supported at the Window level only by GMA.
 N/A N/A Yes (see note) 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 Mac® platforms, using "tool" is not effective.

 Yes No No No
defaultTTFColor

Defines the default color used for TTF icons.

All icons displayed in the window using this style default get the color specified in the defaultTTFColor attribute.

The value for this attribute must be an RGB specification or a named color as listed in Colors.

For more details about TTF icon usage see Using a simple image name (centralized icons).

 Yes Yes Yes Yes
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 pop-up window to the front; to be used with care, as it can annoy the end user.
  • "statustip" adds a small "down" arrow button that shows the pop-up once the user clicks on it; useful to display very long text.
  • "both" will display the comment text in a pop-up window and then in the status bar.
 Yes No No 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.

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

 Yes Yes No No
formScroll

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

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

 Yes No No No
ignoreMinimizeSetting

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

To be used when minimized windows are not to be shown minimized when reopened.

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

 Yes No No No
iosRenderSystemActions

On iOS devices, indicates if default action views must be rendered with iOS standard icons and labels (yes, the defaut), or must use the text and image attributes of the corresponding action (no).

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

The iosRenderSystemActions is taken into account depending on the image action attribute usage:

  • If no image and no text attribute is used, GMI always uses the system action rendering, no matter what the value of iosRenderSystemActions is.
  • If an image attribute is used, the image is always used to render the default action view, no matter what the value of iosRenderSystemActions is.
  • If only a text attribute is used (no image attribute), iosRenderSystemActions defines if the iOS system action rendering is used (yes, the default) or if the text attribute is used (no)

See also iOS default action views decoration.

 N/A N/A N/A Yes
iosTintColor

On iOS devices, defines the color for items used in the navigation bar, toolbar, and some items in the forms (Buttons, SpinEdit, Radiogroups, row check mark, and disclosure indicators in list views).

This style attribute does not apply to MENU with STYLE=dialog/popup.

 N/A N/A N/A Yes
iosNavigationBarTextColor

On iOS devices, defines the text color of the navigation bar.

 N/A N/A N/A Yes
iosNavigationBarTintColor

On iOS devices, defines the background color of the navigation bar.

 N/A N/A N/A Yes
iosToolBarTintColor

On iOS devices, defines background color of the toolbar.

 N/A N/A N/A Yes
iosTabBarTintColor

On iOS devices, defines the background color of the tab bar.

The iOS tab bar is created with a TYPE=NAVIGATOR window.

 N/A N/A N/A Yes
iosTabBarUnselectedColor

On iOS devices, defines the color of unselected items in the tab bar.

This attribute works only for TTF icons. Use iosTintColor to define the color for selected tab bar items.

The iOS tab bar is created with a TYPE=NAVIGATOR window.

 N/A N/A N/A Yes
materialFABActionList

Defines a comma-separated list of action names that are bound to the Floating Action Button (FAB button), on a device following the material design guidelines. To be used in conjunction with the materialFABType attribute. The order of the actions define which action is triggered when the FAB button is tapped, and several matching actions are active.

The default list of actions is: "new,append,insert,update,edit"

 No No Yes No
materialFABType

Controls the Floating Action Button (FAB button) on a device following the material design guidelines.

Possible values are:
  • "single" (default) - the FAB button is shown and maps to the first active action defined in the materialFABActionList attribute.
  • "none" - no FAB button must be displayed.
 No No Yes No
menuPopupPosition

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

Values can be:
  • "cursor" (default) - the pop-up menu appears at the cursor position.
  • "field" - the pop-up menu appears below the current field.
  • "center" - the pop-up menu appears at the center of the screen.
  • "center2" - the pop-up menu appears at the center of the current window.
 Yes No No 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" brings a pop-up window to the front; to be used with care, as it can annoy the end user.
  • "statustip" adds a small "down" arrow button that will show the pop-up once the user clicks on it; useful to display very long text.
  • "both" will display the comment text in a pop-up window and then in the status bar.
 Yes No No No
position

Indicates the initial position of the window.

Values can be:
  • "default" (default): the windows are displayed depending on the window manager or browser rules.
  • "field": the window is displayed below the current field (works as "default", when current field does not exist). The windowType style attribute must be "modal".
  • "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).
    Note: "previous" is not supported by GBC.
  • "center": the window is displayed in the center of the screen.
  • "center2": the window is displayed in the center of the current window.
    Note: "center2" is not supported by GBC.

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

 Yes Yes (see notes) No No
ringMenuButtonSize

Defines the width of buttons for default action views (MENU instruction).

By default, buttons are sized depending on the text and/or image.

This attribute gets a size specification as follows:
  • <number>em: a number followed by the "em" unit (such as "20em"), defines a size relative to the height of the current font.
  • "normal", "shrink", "tiny", "small", "medium", "large" or "huge". When using "normal" and "shrink", buttons are sized depending on the text or image, where "shrink" uses the minimum size needed to display the content of the button.
 Yes Yes No No
ringMenuButtonSpace

Defines the space between buttons for default action views (MENU instruction).

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

 Yes No No No
ringMenuButtonTextAlign

Defines the text alignment inside buttons for default action views (MENU instruction).

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

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

 Yes Yes No No
ringMenuButtonTextHidden

Defines the text visibility inside buttons for default action views (MENU instruction).

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

 Yes Yes No No
ringMenuDecoration

Defines the decoration of the menu panel (MENU instruction).

Values can be "auto" (default), "yes", "no" and "dockable".

 Yes No No No
ringMenuHAlign

Defines the alignment of the ring menu frame (MENU instruction).

This attribute takes effect when ringMenuPosition is "top" or "bottom".

Values can be "left" (default), "right" or "center".

 Yes No No No
ringMenuPosition

Defines the position of the ring menu frame (MENU instruction).

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

 Yes Yes No No
ringMenuScroll

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

Values can be "0" or "1" (default).

 Yes No No No
ringMenuScrollStep

Defines how the ring menu scrolls 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 No No
sizable

Defines if the window can be resized by the user.

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

With the GDC when using "auto", the window becomes resizable if the content of the first displayed form has resizable elements, for example when using a form with a TABLE container or an TEXTEDIT with STRETCH attribute.
Note: With the GDC on Linux® and Mac platforms, some window managers do not allow the size of a window to be frozen and therefore, sizable set to "no" may have no effect.
With GBC:
  • On a normal window, 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.
  • On a modal window, when set to "no", the end-user cannot resize the modal window.
 Yes (see note) Yes No No
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 No 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 No No
startMenuPosition

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

Values can be:
  • "none" (default): the start menu 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 pop-up window that can be opened with a shortcut (see startMenuShortcut).
 Yes Yes No No
startMenuShortcut

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

Default is "control-shift-F12".

 Yes No No 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" (default), "large" or "huge".

The size depends on the font used for the start menu.

 Yes No No No
statusBarType

Defines the type of status bar the window displays.

See Statusbar types for all possible values.

Default is "default".

 Yes No No No
tabbedContainer

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

Note: For the GDC, tabbedContainer=yes indicates that the WCI container must display the child application windows in a folder tab.
Note: For the GBC (WCI is not supported), if a window of an application uses tabbedContainer=yes, every application except the one hosting the tabbed container is embedded in a tab container generated by GBC. When using this style attribute, the GBC side bar is replaced by the StartMenu, which is mandatory when tabbedContainer=yes.
 Yes (see note) Yes (see note) No No
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 No 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 disappears.

A value of zero specifies an infinite time: The thin scrollbar remains visible while the record list can be scrolled (during dialog execution).

A negative value specifies that the scrollbar must always be hidden.

Default is 1 second.

 Yes Yes No No
toolBarDocking

Defines if the toolbar is movable and floatable.

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

 Yes No No No
toolBarPosition

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

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

 Yes No No No
windowMenu

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

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

 Yes No No 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" (default).

When value is "auto", the option is enabled depending on the window type.

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 No No
windowOptionMaximize

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

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

When value is "auto", the option is enabled depending on the window type.

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 No 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" (default).

When value is "auto", the option is enabled depending on the window type.

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 No No
windowState

Defines the initial state of a window.

Values can be "normal" (default), "maximized", "minimized" or "fullscreen".

 Yes No No No
windowSystemMenu

Defines if the window shows a system menu.

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

When value is "auto", the system menu is enabled depending on the window type.

 Yes N/A No No
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 over all other windows, typically used for temporary dialogs.
 Yes Yes No No