FGLPROFILE: GUI configuration

This table shows Four Js Business Development Suite (BDS) FGLPROFILE entries related to GUI configuration which are desupported in Genero Business Development Language.

Table 1. BDS/WTK FGLPROFILE entries related to GUI configuration which are desupported in Genero
Entry	Description of the BDS feature	Genero equivalent
`fglrun.interface`, `fglrun.scriptName`	These entries defined the TCL configuration and script to be send to the WTK front-end.	There is no equivalent in Genero.
`fglrun.guiProtocol.*`	These entries were used to configure the communication protocol with WTK front-end.	In Genero you can control this with gui.protocol.* entries.
`fglrun.error.line.number`	This entry was used to define the number of lines to be displayed in the error message line.	You can control the aspect of the error line with the Window style attribute called `statusBarType`.
`gui.useOOB.interrupt fglrun.signalOOB`	These entries were used to configure or disable Out Of Band signal on the GUI protocol socket to avoid problems on platforms not supporting that feature. OOB signal was used to send interruption events the program executed is processing.	Genero supports interruption event handling with a predefined action name called interrupt. You can bind any sort of action view (button in form, toolbar or topmenu item) with this name. Interrupt events are sent asynchronously with the new Genero GUI protocol and don't use OOB signals any longer. See User interruption handling for more details.
`Sleep.minTime`	This entry was used to define the number of seconds before the interrupt key button appeared on the screen window when the program is processing.	Genero supports interruption event handling with a predefined action name called interrupt. You can bind any sort of action view (button in form, toolbar or topmenu item) with this name. Interrupt events are sent asynchronously with the new Genero GUI protocol and don't use OOB signals any longer. See User interruption handling for more details.
`gui.watch.delay`	This entry was used to define the number of seconds before the mouse cursor displays as a wait cursor, when the program is processing.	Genero supports interruption event handling with a predefined action name called interrupt. You can bind any sort of action view (button in form, toolbar or topmenu item) with this name. Interrupt events are sent asynchronously with the new Genero GUI protocol and don't use OOB signals any longer. See User interruption handling for more details.
`gui.bubbleHelp.*`	These entries were used to enable and configure tooltips displaying field COMMENT text.	Genero front-ends display bubble-help with field COMMENT text by default.
`gui.controlFrame.scroll.*`	These entries were used to show and configure a scrollbar in the action panel displaying ON KEY or COMMAND buttons.	Genero front-ends display control frame scrolling buttons by default when needed. See also Window style attributes like `ringMenuScroll`.
`screen.scroll`	This entry was used to get scrollbars in the main window when the form was too big for the screen resolution of the workstation.	With Genero, by default, each program window is rendered as a distinct GUI window by the front-end. Window aspect can be controlled with style attributes. See Window style attributes for more details.
`gui.screen.size.x` `gui.screen.size.y` `gui.screen.x` `gui.screen.y` `gui.screen.incrx` `gui.screen.incry`	These entries were used to configure the size and position of the main screen window with the WTK front-end.	In Genero, each program window is rendered as a distinct GUI window by the front-end. There is no equivalent for these options. However, you can use the traditional mode to render program windows in a single parent screen window and with BDS/WTK.
`gui.screen.withvm`	This entry was used to integrate with the X11 window manager (allowing move and resize actions).	There is no equivalent in Genero.
`gui.preventClose.message`	This entry was used to display an error message to the user attempting to close the main GUI window with CTRL-F4 or the cross-button on the right of the GUI window title bar.	In Genero, each program window is rendered as a distinct GUI window by the front-end. You can use the close action to control window close events. See Implementing the close action for more details. See also ON CLOSE APPLICATION program option.
`gui.key.doubleClick.left`	This entry could be used to define the key to be returned to the program when the user double-clicks on the left button of the mouse.	You can use the DOUBLECLICK attribute to define the action to be invoked when the user double-clicks on a Table container.
`gui.key.click.right`	This entry could be used to define the key to be returned to the program when the user clicks on the right button of the mouse.	You can configure context menus with the CONTEXTMENU attribute in action attributes.
`gui.key.add_function`	This was used to define the offset to identify SHIFT+Fx keys.	There is no equivalent in Genero.
`gui.key.x.translate`	These entries were used to map keys. For example, when the user pressed Control-U, it was mapped to F5 for the program.	There is no equivalent in Genero.
`gui.key.radiocheck.invokeexit`	This entry defined the key to select the RADIO or CHECK field and move to the next field.	There is no equivalent in Genero.
`gui.mswindow.button`	This entry defined the aspect of buttons on Windows® platforms.	There is no equivalent in Genero: Front-ends will use the current platform theme when possible.
`gui.mswindow.scrollbar`	This entry got MS Windows scrollbar style.	There is no equivalent in Genero: Front-ends will use the current platform theme when possible.
`gui.scrollbar.expandwindow`	When set to true, the WTK front-end expanded the window automatically if scrollbars are needed in a screen array.	There is no equivalent in Genero.
`gui.fieldButton.style`	This defined the style of BMP field buttons.	There is no equivalent in Genero.
`gui.BMPbutton.style`	This defined the style of FIELD_BMP field buttons.	There is no equivalent in Genero.
`gui.entry.style`	This entry defined the underlying widgets to be used to manage form fields.	There is no equivalent in Genero.
`gui.user.font.choice`	This entry is set to true to allow the end user change the font of the application screen window.	Genero front-ends allow the user to change the font. See front-end specific documentation for option configuration.
`gui.interaction. inputarray.usehighlightcolor`	This entry was used to highlight the current row during an INPUT ARRAY.	The current row highlighting can be controlled in Genero with the Table style attribute `highlightCurrentRow`.
`gui.form.foldertab.multiline` `gui.folderTab.input.sendNextField` `gui.folderTab.x.selection`	These entries configure folder tabs and define the keys to be sent when a page is selected by the user.	Genero supports folder tabs with the FOLDER container in LAYOUT. An action can be defined for each folder PAGE.
`gui.keyButton.position` `gui.keyButton.style` `gui.button.width`	These entries define the aspect of action panel buttons associated to ON KEY actions in dialogs like INPUT.	Default action views aspect and position can be controlled with Action Defaults attributes and with Window style attributes.
`Menu.style` `gui.menu.timer` `gui.menu.horizontal.*` `gui.menu.showPagerArrows` `gui.menuButton.position` `gui.menuButton.style`	These entries define the aspect of action panel buttons associated to COMMAND [KEY] actions in MENU.	Default action views aspect and position can be controlled with action attributes with window style attributes.
`gui.empty.button.visible`	This entry is used to hide action panel buttons without text. By default, the empty buttons are visible but disabled.	Default action views aspect can be controlled with action attributes. Use for example the `defaultView` attribute to display a default button for an action.
`gui.containerType` `gui.containerName` `gui.mdi.*`	These entries configure the WCI windows in BDS.	To define WCI containers and children in Genero, use the ui.Interface methods. See Window containers (WCI) for more details.
`gui.toolBar.*`	These entries define the toolbar aspect in BDS.	Toolbar definition has been extended in Genero. See ToolBars for more details.
`gui.statusBar.*`	These entries define the status aspect in BDS.	The StatusBars are defined with Window presentation style attributes. See Presentation Styles for more details.
`gui.directory.images`	This entry defines the path to the directories where images (toolbar icons) are located, on the front-end workstation.	See front-end documentation for image files located on the workstation. With Genero, image files can be located on the application server and automatically transmitted to the front-end based on the FGLIMAGEPATH environment variable.
`gui.display.<source>`	These entries redirect the ERROR / MESSAGE / COMMENT text to a specific place on the GUI screen.	The rendering of ERROR, MESSAGE or COMMENT can be configured with Window style attributes in Genero. However, it is not possible to customize keyboard NumLock / CapsLock status in Genero. See Presentation Styles for more details.
`gui.local.edit` `gui.local.edit.error` `gui.key.cut` `gui.key.copy` `gui.key.paste`	These entry enables and configures cut/copy/paste local keys in WTK.	Cut/Copy/Paste are defined as front-end local actions in Genero. You can bind action views with `editcut`, `editcopy`, `editpaste` predefined action names. See Dialog actions for more details.
`gui.key.*`	These entries were used to map physical key to a virtual key used in programs. For example:`gui.key.interrupt = "control-c"`	Cut/Copy/Paste are defined as front-end local actions in Genero. You can bind action views with editcut, editcopy, editpaste predefined action names. See Dialog actions for more details.
`gui.workSpaceFrame.nolist`	This entry defines the aspect of fixed size screen arrays in forms, to render each array cell as an individual edit field.	There is no equivalent in Genero.