Bug 173613 - configuring: (auto)hide and "windows can cover" are not mutually exclusive
Summary: configuring: (auto)hide and "windows can cover" are not mutually exclusive
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Unmaintained
Component: panel (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-26 17:39 UTC by Maciej Pilichowski
Modified: 2008-10-26 20:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2008-10-26 17:39:36 UTC 
Version:            (using KDE 4.1.2)

configuring: (auto)hide and "windows can cover" are not mutually exclusive

And in configure menu of panel -- they are.
Comment 1 Aaron J. Seigo 2008-10-26 19:09:18 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.
Comment 2 Maciej Pilichowski 2008-10-26 19:20:46 UTC 
> 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.
Comment 3 Aaron J. Seigo 2008-10-26 20:18:53 UTC 
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.