(sort of resolved but the request remains): Show hourglass when loading Configuration

[JLoftus]

OK, well, resolved (sort of).

I started with a clean Windows boot, with as much startup stuff disabled as possible, and sure enough, the configuration dialog loaded almost instantly.

Then, one by one, I began running each of my startup programs, and testing the configuration load after each one. Gradually, the configuration dialog load time increased, until I had all of my startup stuff running, but the delay for the dialog was still "only" about 2-3 seconds.

Then, I began running all the apps I normally use, and checked after each one, again, the time gradually creeping up, 4, 5, 6 seconds with just about everything open that I usually have running (which is a lot).

It was after I started all the WSA apps I use, that the delay was hitting about 6 seconds. Still, I can live with 6 seconds (here, an hourglass still would be welcomed!)... but still, I could not identify what was causing the REALLY long delays, 15, 20, 30 seconds, even longer.... until...

I ran a WebCatalog app, in this case, Google Voice. WebCatalog, for anyone not familiar (https://webcatalog.io/webcatalog) is a really fantastic application for turning any website into an app, thus eliminating the need for consuming an open web browser's tab, and more importantly, the screen real estate of that tab. Many sites that have been turned into apps using WebCatalog can consume very little screen space, if all that is needed is a small display and/or some buttons, etc. There are many examples of where this can be very useful. One of the downsides I have observed to using WebCatalog, is that for each app that is created, a number of processes are launched (similar to how you see many instances of Edge, Firefox, Chrome, etc, more than the number of visible tabs).

When I ran the Google Voice WebCatalog app, the XY Configuration Dialog load time went from about 6 seconds to 14 seconds. I tried increasing the priority of XY's process to High, this made no difference. I then used Task Manager to change the priority of each of the Google Voice app's processes to low, and this finally returned the Configuration Dialog's load time to "only" 7 seconds. Again, I can live with 7 seconds, but an hourglass would still be very appreciated here.

Since I already run an AutoHotKey main script, I can simply add setting the Google Voice priorities to low, that will at least automate that bit (of course that will require me to reload the AHK script after launching the GV App. Yes, I know this can be done via commandline when launching the app, but I don't think that will cause the multiple processes to change to low. Might take some digging there.)
EDIT: Found this, look at Prio https://www.raymond.cc/blog/permanently ... with-prio/
EDIT2: Nix, doesn't seem to work on Win11. Will try ProcessLasso (EDIT3: ProcessLasso works great for this.)

So, while not ideal, at least I have an identified cause and reasonable "mitigation" to this issue (still 7 seconds is not great). Hopefully Don will still consider maybe adding an hourglass since the main window is blocked during the loading any way.