Summary: | Dashboard should always be above all windows, even if windows are checked "always on top" | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | kdeuser56 |
Component: | general | Assignee: | Sebastian Kügler <sebas> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | aleixpol, bhush94, gaantonio, kde, kdeuser56, notmart, simonandric5, thomas.pfeiffer |
Priority: | NOR | Flags: | aleixpol:
Usability+
|
Version: | 5.2.90 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
kdeuser56
2014-08-24 22:30:25 UTC
I agree. The dashboard is a temporary mode used to show Plasmoids which would otherwise be covered by windows. I see no use in keeping windows above the dashboard: When a user activates the dashboard, they want to interact with widgets, not windows. No question, but the problem is actually a technical one. I tried solving it with kwin window scripts, but that seemed impossible, because I wasn't able to find a way to set "always on top" in an absolute manner (meaning above *all* other windows, no matter if they are marked on top too). You can create a rule for the dashboard to always stay on top. That would reproduce the problem of plasma 4 dashboard though: the panel is non interactive, which is a drawback imho. So to solve this, the dashboard needs to be marked on top and the panel on top of the dashboard. However only handling the panel case is not enough, e.g. krunner could be invoked too from dashboard, and that would appear inaccessible hidden under the dashboard layer. Plasma 5 introduced a lot of regressions regarding proper window management (e.g. on top windows can cover the logout dialog), but at the moment I am not in the mood to run after those, especially since most devs wont be interested in such minor stuff and I myself currently suspended learning to code. Plasma doesn't have a dashboard any more, thus we cannot fix this bug any more. |