As you pointed out, there's a page that explains how to change the loading animation here:
http://www.profoundlogic.com/docs/displ ... +Animation
The code you see on that page is JavaScript code. The example chooses to run that JavaScript code when the web page is loaded at the start of all sessions, but that's not a requirement -- you can run it at any time. (Or, perhaps I should say, anywhere that you can insert JavaScript code... but that's nearly any time.)
The tricky part here is that the loading animation starts running before the screen is loaded, so the code can't be in the screen itself. Makes sense if you think about it... it's the loading animation, so it has to begin running BEFORE the screen loads... so how can you run it before your screen is loaded from the server? See what I mean? tricky.
Its hard for me to suggest a solution because I'm not familiar with your application, but...
1) Given that this screen is displayed continuously, maybe it's okay to have the "default" loading animation for the first time the screen is displayed, but then have the changed one for subsequent displays? If so, you can insert the code in the screen's "onload" or "onsubmit" event.
2) If the animation must be changed prior to the first display of the screen, maybe it can be set in a prior display? If necessary, you could write a separate screen just for this... have it change the animation, and then immediately submit control back to the server (with something like pui.click or presskey("enter"), etc). Then it could display the screen that's repeated continuously with the proper animation.
3) Another thought, if it absolutely must apply to every single screen in the session (but nowhere else) would be to have a separate HTML page that starts this vs. other applications. then that page could set it at the start.
4) If you don't like the separate page idea, it could run in a "settings.js" like the example, but use an "if" statement to control whether the animation is changed or not. for example, maybe you'd stick a parameter in the URL to control it, and then settings.js (or whatever you call your start JS file) could look for that parameter.
do any of these options make sense in your application?