Try to get QT To work on windows. - #9702

I haven't worked with this code recently and I don't know why we have a regression, but as a general rule, threads at the heart of our event loop system have been historically nothing but a source of pain. A long time ago, we were able to move away from threads (the original solution for GUI integration dating back to ~2003/4), and that was a huge gain in stability.

We should really think long and hard about how to figure out a non-thread solution.

For reference, this is an attempt to fix #9652.

Agreed I would prefer to not use thread, but it was suggested so I tried.

Something like that would be the alternative I guess.

That sounds a bit more palatable than a threads solution (plus, it's what we've used for years, so it has the benefit of being battle-tested).

That sounds a bit more palatable than a threads solution (plus, it's what we've used for years, so it has the benefit of being battle-tested).

I'll try.

I like #9702 a lot more, and it's working for me. We've had headaches with eventloops in threads for years, from the old -wthread days, so I'm happy that we have a solution that doesn't require reintroducing a thread for this.