UserInterface style attributes

UserInterface presentation style attributes define general options related to the application user interface.

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.

androidKeepForeground (GMA / Androidâ„¢ specific)

Use the androidKeepForeground style attribute to control the way the GMA forces Android to keep your app alive:

An Android app can switch between foreground to background states.

The runtime system part (fglrun) of a Genero Android app can be in the foreground state and still active, while the front-end part (GMA) is visually in the background.

By default, when the app goes to background state, a notification is shown by GMA to give a higher priority to the app, and to prevent Android stopping the app when resources are required for other apps. The notification disappears, when the app returns to foreground state.

Values can be:
  • "yes" (default): The app remains in foreground state: to keep it in foreground state, a notification is displayed when the visual part of the app goes background.
  • "no": The app can switch between foreground and background state. No notification is displayed to force the app to remain in foreground state, and the Android system may stop the app at any time.
Important: When using androidKeepForeground=no, Android may stop the app at any time. Make sure that your application code is ready for this.

applicationListVisible

The application list is defined by the set of programs running concurrently and displaying to the front-end. Concurrent programs may be started directly (from the command line for example), or as a chain of programs using RUN WITHOUT WAITING. The application list is rendered as a vertical bar on the left of the window container.

The applicationListVisible style attribute defines if the application list is visible to the end user. This style attribute is taken into account for the first program that displays to the front-end. All sub-sequent settings for applicationListVisible in new application runs do not impact the application list visibility.

Values can be:
  • "auto" (default): The application list becomes visible, when there is more than one running programs displayed by the front-end, except when the conditions described below apply.
  • "yes": The application list is always visible, even if only one program is displayed by the front-end, except when the conditions described below apply.
  • "no": The application list is always hidden.
The application list is always hidden in the following conditions:
  1. On GDC/Desktop, when each program displays in a dedicated window container (the desktopMultiWindow style attribute is set to "yes")
  2. On GAS/Browser, when each program displays in a dedicated browser tab (the browserMultiPage style attribute is set to "yes")

See also Containers for program windows.

browserMultiPage

When using a GAS/web browser front-end, defines whether child programs started with RUN WITHOUT WAITING are displayed in the current browser tab, or in a new browser tab.

The browserMultiPage style attribute only works, if the application having this style is the first of the session.

When starting a child program with a RUN command not using the WITHOUT WAITING clause, the child program windows are always displayed in the same browser tab as the parent program.

Values can be:
  • "no" (default): All started child programs display in the current browser tab.
  • "yes": All started child programs get a dedicated browser tab.
Note: When using browserMultiPage=yes, by default, when the main/parent program is terminated while child programs (started with a RUN WITHOUT WAITING) are still running and displaying in their dedicated browser tabs, the browser tab of the parent program will remain open and show a message, until all child programs are terminated. The GAS XCF configuration parameter CloseAllOnMainExit can be set to YES, to force all child programs to terminate automatically, when the main/parent program terminates.

See also Containers for program windows and the RUN command.

desktopMultiWindow

When using the GDC/desktop front-end, defines if child programs started with RUN ... WITHOUT WAITING are displayed in the same window container or get a dedicated window container of the operating system.

When starting a child program with a RUN command not using the WITHOUT WAITING clause, the child program windows are always displayed in the same desktop window container as the parent program.

Values can be:
  • "no" (default): A single window container is created for all applications. All started child programs display in the same container. The application list can be used to switching between applications.
  • "yes": Multiple window containers are created for each running program. All started child programs get a dedicated window container.

See also Containers for program windows and the RUN command.

reverse

Global configuration option to display forms in reverse mode and enable right to left input, for right-to-left language support.

Values can be:
  • "no" (default): Display forms for left-to-right languages.
  • "yes": Display mirrored forms for right-to-left languages.

windowListVisible

The window list is defined by the set of windows opened by the current program and opened by all child programs started with a waiting RUN. The purpose of the window list is to show the content of inactive windows, opened before the current active window.

By default, the window list option is visible on the top left of the chromebar.

The windowListVisible attribute defines if the window list is visible to the end user.

Values can be:
  • "yes" (default): The window list is visible, when there more than one window is opened by the program or child programs started with a waiting RUN.
  • "no": The window list is always hidden. The stack of inactive windows cannot be seen. Only the current active window is available.

See also Containers for program windows.