Activating multiple screens on button event

Greetings community,

I have run into a problem with the scripting and hope you can help me figure out what the problem is.

Tried to describe the structure of my screens in the diagram below.

On the root screen there's a screen window object (swMainContent) containing my MANUAL_NAVIGATION_SCREEN which at its turn has another screen window displaying MANUAL_MODE_PG_1.

The button on this page is supposed to change the content of the swMainContent to MANUAL_CONTROL_SCREEN and assign MANUAL_0108005_0108030 to a screen window inside MANUAL_CONTROL_SCREEN (the screen we just opened).

At the moment I only manage to open the screen in swMainContent but the swManualControlContent stays intact.

Is my desired functionality even possible to achieve? Tried different ways to get the object path of the screen window but still no result.

Stefan Arcularius

Hi,

I am pretty sure that the problem you are having is with the screen change itself. The ChangeScreen method should always be the last method called when changing the screen to which the event belongs. Otherwise, the script will stop after the screen change to free up resources. However, in your case, this information would not be helpful since you want to change two screens in the same object path.

This is an interesting question, and one I haven't encountered before. I have three possible solutions in mind, but I don't know which one would help because I'm not sure of the conditions under which a script is aborted on screen change.

• Use the event buttons to modify an internal tag - if you want to allow multiple clients on a PC runtime, use the "local session" scope. In your root screen, use the dynamization of a parameter of your choice to trigger on this tag and make your screen changes there.
• Hoping that the Promise will not be canceled, using ChangeScreenAsync would probably solve your problem.
• The third approach you can try is to use a global script that calls the screen changes.

It would be interesting for me - and probably someone else in the community - to learn about the solution you used. Thanks in advance!

Kind regards
Stefan

Hi Stefan and thank you for your prompt answer and suggestions.

The problem appears to be in the screen change indeed. The script is only running until first screen change instruction is encountered and there's nothing to do about it atm. This was one of my first thoughts too so I already tried the "ChangeScreenAsync" hoping it will solve my problem but the magic didn't happen.

As much as I wanted to avoid using local tags for screen navigation (already doing that on some of the other screens) because it complicates the future customization/updates for non-dev users, this is exactly what I did.

In the button event script, apart from activating the screen, a local scope string tag is set from a GlobalModule array based on the required index (have multiple buttons with specific pages to be opened).

Might be not the finest way to do it but seems to be the best workaround for my needs.

Some screenshots of my solution are attached below, hopefully my experience and explanation comes in handy for other users. Cheers!