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
This commit is contained in:
parent
91faa589c7
commit
8e78ccac46
1 changed files with 0 additions and 8 deletions
|
@ -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!
|
||||
|
|
Loading…
Reference in a new issue