Minor UI bugs about universal_gtao_booster

[QuickNET-Tech]

Sounds like WinAPI being a pita. For the message box I can try a different flag on the message box (probably the right solution), or if I can somehow get a handle to the window I can force it on top (a hack if the proper solution doesn't work). Messagebox and the config should be handled post-window and I set the foreground flag, there's another more aggressive flag that might help. As for the console, it wouldn't be the first time I've seen it not work as it should, which is why in the code I'm actually extra forceful and actively destroy the window after freeing the console. The comment where I do that is amusing in the context of it not working:

Universal_GTAO_Booster/log/log.c

Line 70 in 3146319

DestroyWindow(consoleWindow); // shouldn't be necessary at all, but a little force won't hurt

I'll see if I can reproduce asap, thanks.

[QuickNET-Tech]

If you're able to pull and build, I've made a few tweaks that should hopefully help. Unfortunately I've not been able to reproduce so...

[tostercx]

Nope, both still reliably happen every time for me! (Except now the R* logo patch is applied too late sometimes). Really surprised DestroyWindow doesn't do anything.

Unfortunately I've not been able to reproduce so...

Yeah, if my guess is right, it's timing based, so it would be a PITA to recreate/debug :/
Could be something else on my system as well (running Steam version/windowed if that matters).

It's not too big of a deal - could always fix later if more people complain. Can either disable the console or minimize it as a workaround.

Gonna try debugging it some more later.

[QuickNET-Tech]

Tbh this pretty much sums up my experience with the WinAPI, it does what it wants when it wants.

Reverted 4e4b5b4