Members of the KDE Community are recommended to subscribe to the kde-community mailing list at to allow them to participate in important discussions and receive other important announcements

Commit 8af6d4f5 authored by Vlad Zahorodnii's avatar Vlad Zahorodnii

[x11] Emit clientRemoved after client was removed

Currently, there is a guarantee that a client, which is about to be removed,
is no longer in the stacking order(both in constrained and unconstrained)
when Workspace::removeClient is called. However, because the client gets
removed from m_allClients after clientRemoved is emitted, it can be
re-inserted back into the stacking order.

In general, the pattern is to do some work and then notify others about
what you've done by emitting a signal. In the case of Workspace::removeClient,
we emit clientRemoved way before the client actually gets removed.

CCBUG: 392412
CCBUG: 400854

Test Plan:
* Enable the following script:

workspace.clientAdded.connect(function (client) {
    if (client.skipTaskbar || client.modal || client.transient) {
    workspace.desktops = workspace.desktops + 1;
    workspace.currentDesktop = workspace.desktops;
    client.desktop = workspace.currentDesktop;

workspace.clientRemoved.connect(function (client) {
    if (client.skipTaskbar || client.modal || client.transient) {
    workspace.desktops = workspace.desktops - 1;

* Open an app, close the app.

Reviewers: #kwin, graesslin

Reviewed By: #kwin, graesslin

Subscribers: graesslin, kwin

Tags: #kwin

Differential Revision:
parent a28410d8
......@@ -661,8 +661,6 @@ void Workspace::addUnmanaged(Unmanaged* c)
void Workspace::removeClient(Client* c)
emit clientRemoved(c);
if (c == active_popup_client)
if (m_userActionsMenu->isMenuClient(c)) {
......@@ -704,6 +702,8 @@ void Workspace::removeClient(Client* c)
if (c == delayfocus_client)
emit clientRemoved(c);
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment