subScreen | a JS tool that let you take screenshot of many hosts | Image Editing library

Here is the new code:

You can copy paste run full code below
You can create a List and show with appbarList[_selectedIndex]

code snippet

That's a well-known issue with controls. If you instantiate any GUI control (in your case, it's the ALV grid) inside a container in which there was already a control which has not been freed up (in your case, the ALV grid first instantiated using cl_salv_table=>factory), then the old control still shows up, the new one is not shown.

Two solutions :

• Either you keep instantiating the control, but then you must free the previous control. For this, you must call control->FREE( ) followed by the statement FREE control. This method is available for all controls (even the container itself can be freed, all its inner controls are then freed up).

• Or you change the logic by instantiating the control only once, and you refresh its contents.

Special case: some controls may be wrapped by some wrapper classes which don't give access to the control (SALV classes for instance), so the easy way is to free the container to which the control is attached.

It is difficult to interpret exactly what you are attempting to do. For example, why are you adding a RoundedButton to a BackLabel in the __init__() method of your BackLabel? Anyway, here is a simpler version of your code that does what I think you want. A couple things to note: In order to position a Widget meaningfully, it must have a reasonable size. The default size of any Widget is the same as its parent, so positioning it doesn't really make sense. So my code below sets the size of your RoundButton (which requires size_hint to be (None, None). Finally, the position can be set (as in the SubScreen rule in the kv below):

Here is what works, it's not pretty.

1. Copy GUI status INLI from program SAPMSSY0 to your own program
2. Change the OK code for the cancel button. To work with your example code, change it to ECAN. Also change the one in the Edit menu to be complete
3. As the first command in your START-OF-SELECTION use SET PF-STATUS 'INLI'. This is assuming you named it the same
4. Change the AT SELECTION-SCREEN to AT USER-COMMAND
5. Activate, test and be amazed

This works because it removes the standard behavior for lists and replaces it with your own, only for the cancel button mind you. Without changing the OK code for cancel the standard SAP code will take over and you have no control over the behavior.

I think it is because SubScreen2 is not in the stack yet. Try this.

REASON:

• The function types of the 2 tabs are defined with the value "P", meaning that the tabstrip works using "local paging", so it needs to work with 2 subscreen areas referring each to one distinct subscreen, so that the actions on the tabs work as expected.

• There are two types of usage of a tabstrip.

  1. Use one subscreen for all tabs ("server paging") So you have to load each data new if the users clicks on a tab.

  2. Use one subscreen for each tab ("local paging") The whole data will be loaded at the beginning of the program.
     NOTE: In the screen layout editor you have to set the parameter FctType to P - local GUI func.

RESOLUTION:

If you want to use the server paging (1), let the function type empty like this :

You need to add the SCM config in the docker-compose.yaml file generated as aprt of in-a-box set up. It goes like this