Skip to content

Commit da8d413

Browse files
authored
Update popups.md
1 parent 6f59405 commit da8d413

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

docs/development/popups.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,24 @@ ENDMETHOD.
5858
#### Separated App
5959
For better source code structure, it's possible to encapsulate popups in separate classes and call them through [navigation](/development/navigation/navigation).
6060

61-
#### Call Stack
61+
Check out for example the popup to confirm:
62+
```abap
63+
METHOD z2ui5_if_app~main.
64+
65+
IF client->check_on_init( ).
66+
client->nav_app_call( z2ui5_cl_pop_to_confirm=>factory( `Can you confirm this?` ) ).
67+
ENDIF.
68+
69+
CASE client->get( )-event.
70+
WHEN z2ui5_cl_pop_to_confirm=>cs_event-confirmed.
71+
client->message_box_display( `the result is confirmed` ).
72+
WHEN z2ui5_cl_pop_to_confirm=>cs_event-canceled.
73+
client->message_box_display( `the result is rejected` ).
74+
ENDCASE.
75+
76+
ENDMETHOD.
77+
```
78+
6279
If you need to manage a stack of multiple popups, remember that abap2UI5 displays only one popup at a time on the frontend. However, you can maintain a popup stack in your backend logic and re-display the previous popup as needed. Check out `Z2UI5_CL_DEMO_APP_161`.
6380

6481
### Popover

0 commit comments

Comments
 (0)