Bug 171454 - Determine new stacking order of windows before animations start
Summary: Determine new stacking order of windows before animations start
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 185707 255110 340497 (view as bug list)
Depends on: 119323
Blocks:
  Show dependency tree / graph
 
Reported: 2008-09-22 15:22 UTC by Will Stephenson
Modified: 2024-05-14 21:38 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Will Stephenson 2008-09-22 15:22:53 UTC 
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    SuSE RPMs

Scenario: Compositing enabled, "Desktop grid" desktop switcher in use.

I have kmail on all desktops and on top.

During the switch animation the windows from the desktop being switched to slide on and cover the kmail window.  At the end of the switch kmail is drawn on top.  This looks bad, worse if kmail is maximised.

Expected behaviour: figure out the window stack before starting the animation, so that the window on top on all desktops stays still, windows from other desktop should slide under it.
Comment 1 Martin Flöser 2009-12-15 23:36:11 UTC 
*** Bug 185707 has been marked as a duplicate of this bug. ***
Comment 2 Martin Flöser 2010-12-18 13:06:33 UTC 
*** Bug 255110 has been marked as a duplicate of this bug. ***
Comment 3 Martin Flöser 2011-03-09 20:29:16 UTC 
root cause is missing support of per-desktop stacking order
Comment 4 Martin Flöser 2014-10-30 13:13:26 UTC 
*** Bug 340497 has been marked as a duplicate of this bug. ***
Comment 5 Justin Zobel 2021-03-10 00:12:37 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.