https://bugs.kde.org/show_bug.cgi?id=409889
--- Comment #5 from Natalie Clarius ---
I don't know if this has been recently implemented or always been there and
just never documented, but it works for me:
> client.stackingOrder
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=409889
Natalie Clarius changed:
What|Removed |Added
CC||natalie_clar...@yahoo.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=409889
Mikhail Skorzhinskii changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |ra...@eml.cc
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=409889
--- Comment #4 from Martin Flöser ---
Please be aware that stacking order would be read only. To manipulate you would
have to use the existing API calls.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409889
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=409889
--- Comment #3 from Vlad Zahorodnii ---
(In reply to Mikhail Skorzhinskii from comment #2)
> Any ETA on implementing this?
That's up to you.
> The task looks doable for me from my unprepared eye, so given the
> information you just shared, I guess I
https://bugs.kde.org/show_bug.cgi?id=409889
--- Comment #2 from Mikhail Skorzhinskii ---
> I guess we could add something like this to the scripting API
Great! I have fears that there are some fundamental problems that prevents
exposing these structures to the scripting API.
> though I'm not
https://bugs.kde.org/show_bug.cgi?id=409889
--- Comment #1 from Vlad Zahorodnii ---
> m_allClients) from workspace.h, which is not sorted at all
We don't maintain stacking order in m_allClients.
There are currently several stacking orders:
* Unconstrained (unconstrained_stacking_order): the
