Hello Marcel,

I can’t really tell you why calling webui::RefreshAllWidgets would cause that particular warning message. Because it just shouldn’t, and I hope some other part of your model contains remainders of your original setup/idea/refreshes when applied to the WinUI app this WebUI app was maybe built ‘from’.

But this is not your real problem or solution for it anyway. Since refreshing the widgets does not work by reloading the page like in a ‘full browser page refresh’. Which is indeed needed if you know that you’ve changed one of your stylesheets.

But in order to do that, some trigger would need to be in place, in the browser, like a piece of script that:

• acts like a custom widget that responds to one of its options changing (by reloading or by doing what the 3rd option suggests)
• monitors page contents for a certain widget-uri to be added to the page and then adding a click handler to it which does the browser refresh. Or,
• does something like the previous, but instead does not reload, but sets the new value of the css custom property (‘theming variable’) that dictates the background color. That would work instantly.

The first is the most ‘AIMMS-like’. But part of our kind of deprecated Custom Widgets setup…

The page monitoring needed for option 2 or 3 is potentially a little bit harmful for overall page performance, but you might not notice it at all either.

Do you have a certain Widget that is the actual trigger for leaving or entering the training mode? Like a button on a specific page? Do you need some pointers or a skeleton script to get you going in that direction?

@MarcelMueller can you check if you have any XML pages in your application? Being old WinUI pages or just data pages saved under Main Project > Pages?