Make hyprctl thread safe
This commit is contained in:
parent
304b93a4f6
commit
883d389bc2
3 changed files with 63 additions and 13 deletions
|
|
@ -3,6 +3,7 @@
|
|||
#include "../managers/InputManager.hpp"
|
||||
#include "../render/Renderer.hpp"
|
||||
#include "Events.hpp"
|
||||
#include "../debug/HyprCtl.hpp"
|
||||
|
||||
// --------------------------------------------------------- //
|
||||
// __ __ ____ _ _ _____ _______ ____ _____ _____ //
|
||||
|
|
@ -133,6 +134,8 @@ void Events::listener_monitorFrame(void* owner, void* data) {
|
|||
g_pAnimationManager->tick();
|
||||
g_pCompositor->cleanupWindows();
|
||||
|
||||
HyprCtl::tickHyprCtl(); // so that we dont get that race condition multithread bullshit
|
||||
|
||||
g_pConfigManager->dispatchExecOnce(); // We exec-once when at least one monitor starts refreshing, meaning stuff has init'd
|
||||
|
||||
if (g_pConfigManager->m_bWantsMonitorReload)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue