From 8e78ccac46299b306430d1a8e0d5b3c9f879c8d6 Mon Sep 17 00:00:00 2001 From: Roman Gilg Date: Thu, 8 Aug 2019 16:42:28 +0200 Subject: [PATCH] Remove X11Compositor requires compositing check Summary: With the split of the Compositor class in X11 and Wayland it is unnecessary to check in X11Compositor if compositing is required since on X it never is. Test Plan: Compiles. Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D23032 --- composite.cpp | 8 -------- 1 file changed, 8 deletions(-) diff --git a/composite.cpp b/composite.cpp index 37d4daea8a..9fef596e54 100644 --- a/composite.cpp +++ b/composite.cpp @@ -911,11 +911,6 @@ X11Compositor::X11Compositor(QObject *parent) void X11Compositor::toggleCompositing() { - // For the shortcut. - if (kwinApp()->platform()->requiresCompositing()) { - // We are not allowed to turn on/off compositing. - return; - } if (m_suspended) { // Direct user call; clear all bits. resume(AllReasonSuspend); @@ -1041,9 +1036,6 @@ void X11Compositor::updateCompositeBlocking() void X11Compositor::updateClientCompositeBlocking(Client *c) { - if (kwinApp()->platform()->requiresCompositing()) { - return; - } if (c) { if (c->isBlockingCompositing()) { // Do NOT attempt to call suspend(true) from within the eventchain!