Is there any way to detect, when something new is displayed like a modal, when Wappler has calculated the variables it needs to calculate… and then use that detection in a show/hide construct?
It would be helpful to prevent some of my modals flashing up old information temporarily for 100ms or so before the new information appears!
Hi,
Not sure if this is possible, since there is no end to the calculations Wappler/DMX does. Its a continuous loop running every few ms.
As a workaround, you can maybe use a flow wherever you are opening the modal, and add a delay after you set your selection variabe and before the model.show is called.
I think by that you mean App Connect
Yes. I tend to use all three as synonyms. 
I usually have two conditional regions in the modal. One set to when the SC actions are executing and the other to when they are not. The one that shows when the SC state executing has a spinner (usually just a font awesome spinner) and maybe ‘loading…’ text. The other region has the content.
Rather than using the ‘Action Toggle’ of the button to open the modal, I use dynamic event for the click to first trigger the SCs and then show the modal.
Thanks for your feedback @sid, that makes sense.
I’d love us to have a tutorial on here about how Wappler is working under the hood in this regard and how we can harness that knowledge to make cleaner and faster user interfaces.
@George, is that some information the team can help us with? Should I make a feature request about it?