Don't invalidate x stacking order prematurely
Workspace::updateStackingOrder() will mark it as dirty if the stacking order actually changes due to a constraint being added or removed.
This commit is contained in:
parent
c9ee2f06db
commit
e29dee951d
1 changed files with 0 additions and 3 deletions
|
@ -570,7 +570,6 @@ void Workspace::constrain(AbstractClient *below, AbstractClient *above)
|
|||
child->parents << constraint;
|
||||
}
|
||||
|
||||
markXStackingOrderAsDirty();
|
||||
updateXStackingOrder();
|
||||
}
|
||||
|
||||
|
@ -599,8 +598,6 @@ void Workspace::unconstrain(AbstractClient *below, AbstractClient *above)
|
|||
}
|
||||
|
||||
delete constraint;
|
||||
|
||||
markXStackingOrderAsDirty();
|
||||
updateStackingOrder();
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue