| Summary: | configuring: (auto)hide and "windows can cover" are not mutually exclusive | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Maciej Pilichowski <bluedzins> |
| Component: | panel | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | aseigo |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Maciej Pilichowski
2008-10-26 17:39:36 UTC
they are mutually exclusive by design. what would be the meaning of a "autohiding panel that windows can be on top of"? a panel that slides out under windows so you can see it? of course not. triggering the unhide would raise and show it above the windows .. in other words there is no point to separating the two and allowing them to be combinable. it's nonsensicle. > a panel that slides out under windows so you can see it? of course not.
Of course -- yes.
1. show panel (it is hidden, so you have to move mouse)
2. run konsole (for example) -- click on the panel
3. now you have to move mouse again, because panel covers konsole
Now step 3. thanks to design is a must, if those options were not mutually exclusive, as they should, there would be no need for moving mouse.
Of course switching those options on/off would be up to the user.
Please reconsider.
leaving as is, because i really don't think this combination of settings makes sense in common use cases and would complicate the inner workings. |