Busy Dialog - Standard
A Busy Dialog blocks the user interface until the currently running operation has been finished. No other activities can be started in parallel.
Z2UI5_CL_SMPC_APP_004
Controls
sap.m
UI5 1.71
The facts
- Repository
- abap2UI5/samples-controls
- Class
Z2UI5_CL_SMPC_APP_004- Source file
z2ui5_cl_smpc_app_004.clas.abap↗- Library
- sap.m
- UI5 entity
sap.m.BusyDialog- Demo kit sample
sap.m.sample.BusyDialog- SAP's own sample
- running at sdk.openui5.org ↗
- Minimum UI5
- 1.71 — the floor abap2UI5 holds its samples to
- In the playground
- runs in the browser, with no system and nothing installed
Keywords: busydialog, busy, dialog, sap.m, indicate, verticallayout, button
Controls it builds
- sap.m.BusyDialog
- sap.m.Button
- sap.ui.core.FragmentDefinition
- sap.ui.core.mvc.View
- sap.ui.layout.VerticalLayout
Read out of the builder chain by the abap2UI5 linter, not from the category this sample is filed under — which is what makes “which samples build one of these” a question the catalogue can answer at all.
Libraries
Run it here
The sample running, in this page — the app on its own, with no editor over it.
Switch to Playground with this code
Nothing is installed and nothing is sent anywhere: the ABAP is compiled to JavaScript in this browser and runs against abap2UI5 itself.
The ABAP
z2ui5_cl_smpc_app_004.clas.abap — 112 lines
Click a number to link to a line — shift-click for a range.
Read it on GitHub ↗
" @keywords busydialog busy dialog sap.m indicate verticallayout button
" @summary A Busy Dialog blocks the user interface until the currently running operation has been finished. No other activities can be started in parallel.
CLASS z2ui5_cl_smpc_app_004 DEFINITION PUBLIC.
PUBLIC SECTION.
INTERFACES z2ui5_if_app.
PROTECTED SECTION.
DATA client TYPE REF TO z2ui5_if_client.
" the original's clearTimeout guard: a timer that outlives a cancel is ignored
DATA check_busy TYPE abap_bool.
METHODS view_display.
METHODS on_event.
METHODS popup_display.
PRIVATE SECTION.
ENDCLASS.
CLASS z2ui5_cl_smpc_app_004 IMPLEMENTATION.
METHOD z2ui5_if_app~main.
me->client = client.
IF client->check_on_navigated( ).
view_display( ).
ELSEIF client->check_on_event( ).
on_event( ).
ENDIF.
ENDMETHOD.
METHOD view_display.
DATA(view) = z2ui5_cl_ui5_view_builder=>factory( ).
view->ele( n = `View` ns = `mvc`
)->a( n = `xmlns` v = `sap.m`
)->a( n = `xmlns:l` v = `sap.ui.layout`
)->a( n = `xmlns:mvc` v = `sap.ui.core.mvc`
)->ele( n = `VerticalLayout` ns = `l`
)->a( n = `class` v = `sapUiContentPadding`
)->a( n = `width` v = `100%`
)->tag( `Button`
)->a( n = `text` v = `Show Busy Dialog`
)->a( n = `press` v = client->_event( `OPEN_DIALOG` )
)->a( n = `class` v = `sapUiSmallMarginBottom` ).
client->view_display( view->stringify( ) ).
ENDMETHOD.
METHOD on_event.
DATA cancel_pressed TYPE abap_bool.
CASE client->get_event( ).
WHEN `OPEN_DIALOG`.
check_busy = abap_true.
popup_display( ).
" the original's simulateServerRequest - close the dialog after 3000ms
client->follow_up_action( val = client->cs_event-start_timer
t_arg = VALUE #( ( `TIMER_FINISHED` ) ( `3000` ) ) ).
WHEN `TIMER_FINISHED`.
IF check_busy = abap_true.
client->follow_up_action( val = client->cs_event-control_by_id
view = client->cs_view-popup
t_arg = VALUE #( ( `busyDialog` ) ( `close` ) ) ).
ENDIF.
WHEN `DIALOG_CLOSED`.
check_busy = abap_false.
cancel_pressed = client->get_event_arg( ).
IF cancel_pressed = abap_true.
client->message_toast_display( `The operation has been cancelled` ).
ELSE.
client->message_toast_display( `The operation has been completed` ).
ENDIF.
ENDCASE.
ENDMETHOD.
METHOD popup_display.
DATA(popup) = z2ui5_cl_ui5_view_builder=>factory( ).
popup->ele( n = `FragmentDefinition` ns = `core`
)->a( n = `xmlns` v = `sap.m`
)->a( n = `xmlns:core` v = `sap.ui.core`
" id added so the backend timer event can close the dialog via control_by_id
)->tag( `BusyDialog`
)->a( n = `id` v = `busyDialog`
)->a( n = `title` v = `Loading Data`
)->a( n = `text` v = `... now loading the data from a far away server`
)->a( n = `showCancelButton` v = `true`
)->a( n = `close` v = client->_event( val = `DIALOG_CLOSED` arg = `${$parameters>/cancelPressed}` ) ).
client->popup_display( popup->stringify( ) ).
ENDMETHOD.
ENDCLASS.
More in sap.m
- Action List Item — Use the Action List Item to trigger an action directly from a list
- Page,Toolbar and Bar — Each screen of a mobile application is typically represented by a 'Page' consisting of a…
- Breadcrumbs sample — Breadcrumbs is useful for displaying link hierarchy
- Button — Buttons trigger user actions and come in a variety of shapes and colors. Placing a button…
- Carousel with Controls — With the Carousel a user can browse through multi-page content by swiping left or right.
- Tri-State Check Box — In this sample, the CheckBox reflects the selection states of its dependent input fields…
- Color Palette in a form — The standalone ColorPalette in a container (sap.ui.layout.SimpleForm).
- Table - Columns — The table shares many features with the list and, in addition, introduces columns. The ta…
- Table Test with OPA — The following example simulates a click on a list item in a table.
- Combo box — The combo box control provides a list box with items and a text field allowing the user t…
- Comparison Pattern — The pattern allows users to select multiple items from an sap.m.Table and display informa…
- Cookie Settings Dialog Pattern — The Cookie Settings Dialog allows you to easily manage the cookie settings according to t…
On this page