Skip to main content
BGuth.1
BGuth.1
Senior
March 1, 2022
Solved

Common pop-up for all screens

  • March 1, 2022
  • 2 replies
  • 1344 views

I need to show a pop-up window when a particular condition satisfies. I created a model window and showed it when the condition satisfies. However, when I have multiple screens, do I have to create this model window each and every screen? Is there a way to create it once and show it no matter whatever screen is currently active? I don't want to change the screen but show the pop-up in current screen itself.

This topic has been closed for replies.
Best answer by Yoann KLEIN

Hello @BGuth.1​ ,

Unfortunately, you will have to integrate your modal window on every screen/class you want to display your popup in. We are currently working on a common BaseClass to implement that kind of functionalities, but it's not deployed yet.

/Yoann

2 replies

Yoann KLEIN
Yoann KLEINBest answer
ST Employee
March 2, 2022

Hello @BGuth.1​ ,

Unfortunately, you will have to integrate your modal window on every screen/class you want to display your popup in. We are currently working on a common BaseClass to implement that kind of functionalities, but it's not deployed yet.

/Yoann

Yoann KLEINST Software Developer | TouchGFX
DSwea.1
DSwea.1
Associate III
March 5, 2022

I'm very happy to hear this and hope that you are prioritizing the common BaseClass so that it is available soon. At present, if one wishes to conform correctly to the MVP model, every single screen that uses a particular popup, widget, or such, must duplicate the code that does so. This goes against every thing I've learned and practiced in years of design and coding.

In my case, I have a common footer that appears on every screen, and includes a time/clock display that must be updated regularly. If the current time is captured in the model (as it should be), then, for every screen in the project, one must call a ModelListener-defined function to pass the time to the Presenter, and then, in turn, a function in the Presenter to pass the time to a function in the View, all of which must be entered on every screen.

Another feature that would be of tremendous value would be to see one's own classes and widgets appear in the Designer. I know this is a challenging and complex undertaking; but every instance where it becomes necessary to add ones objects in code without seeing them in the Designer makes the Designer less and less useful.

DSwea.1
DSwea.1
Associate III
April 23, 2022

An additional comment...

The base class you describe as being under development must allow users to define base classes not only for the View, but the Presenter as well, in order that the base class can define a complete path for messages up and down the MVP stack that will be in place for every screen generated.

Terms & ConditionsAccessibility statement