From 883d389bc283ac6b29b303a94f063e5575f8416f Mon Sep 17 00:00:00 2001
From: vaxerski <43317083+vaxerski@users.noreply.github.com>
Date: Thu, 21 Apr 2022 22:00:03 +0200
Subject: Make hyprctl thread safe

---
 src/events/Monitors.cpp | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'src/events/Monitors.cpp')

diff --git a/src/events/Monitors.cpp b/src/events/Monitors.cpp
index 840602bd..3f1d38e1 100644
--- a/src/events/Monitors.cpp
+++ b/src/events/Monitors.cpp
@@ -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)
-- 
cgit v1.2.3