UIElement Properties

Properties in View Designer

enabled

Specifies whether or not an event can be triggered by a user interaction. If the value is TRUE, the view elements positioned above it are used at runtime to determine the value. This means that if the surrounding container is not enabled, all the containers within this are also not enabled.

In Web Dynpro ABAP "enabled" is always passed down from parent to child. If a UI element lies nested in another UI element that has enabled=FALSE, then this UI element has also enabled=false.

Values	Description
TRUE	View elements positioned above this element are used at runtime to determine the value.
FALSE	View elements positioned above this element are not used at runtime to determine the value.

For an InteractiveForm UI element, enabled is the definition of whether an interactive form or a (not interactive) print form is involved. If the value is TRUE, the form is interactive and ready for input. Use the value FALSE for print-only forms.

Note that the enabled property is not active with an InteractiveForm UIelement.

This property can be personalized by administrators. This property can be assigned the value, false, in the personalization function.

styleClassName
With this property you can create your own style definitions to change the appearance of UI elements (for example, the font color of a Button).
With interface IF_WD_CUSTOM_STYLE_MANAGER (method CREATE_CUSTOM_STYLE) you can create your own style classes. You define the various style definitions for a style class within objects of interface type IF_WD_CUSTOM_STYLE in the form of a name/value list. You can then assign these style definitions to specific UI elements. The value of parameter STYLE_CLASS_NAME of method CREATE_CUSTOM_STYLE must be the same as the value of property styleClassName of the UI element.
This property can be personalized by administrators.

Note

This feature is only available in HTML standards mode. For more information, see UI Control Rendering in Standards Mode, and 1753544 .

Note that setting a style is not always visible. Other properties can dominate and overwrite these. This can have an impact on the present style or on changes made in the future.
Example
A style definition is created and added to the application in the following example. The style definition ensures that the text for buttons that use this style definition is displayed in red:
```
data l_style_manager  type ref to if_wd_custom_style_manager.
data l_style          type ref to if_wd_custom_style.

" Get the custom style manager
l_style_manager =
  wd_comp_controller->wd_get_api( )->get_application( )->get_custom_style_manager( ).

" Create a new custom style with name myButtonStyle for BUTTON elements
l_style =
  l_style_manager->create_custom_style( style_class_name = `myButtonStyle`
                                           element_type     = 'BUTTON' ).
" Set font color to red
l_style->add_style_property( name  = `fontColor`
                               value = `red` ).
" Add custom style
l_style_manager->add_custom_style( l_style ).
```
To assign the style definition to a button, set the button property styleClassName to the value myButtonStyle.

You can find an application example in the system in component WDR_TEST_CUSTOM_STYLES.
For more information, see the system documentation for the following interfaces:
- IF_WD_CUSTOM_STYLE
- IF_WD_CUSTOM_STYLE_MANAGER
tooltip
Quick info text that appears when the user moves the mouse pointer over the UI element. If Screen Reader is supported, extra text is added automatically to the tooltip in order to support accessibility.

Pay attention to the following if an Hot Keys is set for one of the following UI elements: AbstractButton and those UI elements that inherit from this: IconButton, LinkToAction, LinkToUrl, MenuActionItem, ToolBarLinkToAction, ToolBarLinkToUrl: The relevant key combination for the corresponding hotkey is always automatically inserted into the tooltip of the appropriate UI element. If a text already exists for the tooltip, the text for the hotkey is appended to the end.
This property can be personalized by administrators.

visible

Visibility of the interface element.

Both users and administrators can personalize this property.

Values	Description	Can be Set Using Personalization
NONE	The UI element is not visible on the screen and takes up no space.	Yes
VISIBLE	The UI element is displayed on the screen.	No