The entire multi-threading mode was implemented just to allow graphics updates while e.g. dragging or resizing the window.
But that wouldn't be a thing in full-screen mode, and even the current crude, simple threading model is flaky (e.g. randomly freezing due to a race condition on exit... -> #464), the input control updates may be too disjoint from their corresponding reactions, and threading just doesn't really offer any benefits currently, it only has drawbacks (e.g. also making it unnecessarily difficult to let the entire process, not just the current thread, sleep, when idle).
The entire multi-threading mode was implemented just to allow graphics updates while e.g. dragging or resizing the window.
But that wouldn't be a thing in full-screen mode, and even the current crude, simple threading model is flaky (e.g. randomly freezing due to a race condition on exit... -> #464), the input control updates may be too disjoint from their corresponding reactions, and threading just doesn't really offer any benefits currently, it only has drawbacks (e.g. also making it unnecessarily difficult to let the entire process, not just the current thread, sleep, when idle).