| Summary: | Show desktop only activates on the current screen | ||
|---|---|---|---|
| Product: | [Plasma] plasma4 | Reporter: | Mike <mike> |
| Component: | multiscreen | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Mike
2007-12-19 16:17:27 UTC
actually, they aren't the same desktop in the plasma sense. i'm really of two minds on this one ... the idea is that it brings your desktop layer forward: so should *all* desktop layer leap forward, or just the one you are currently active on? i think it's nicer if it's just the one you are currently on as that leaves the door open treating each screen truly independently: consider when you have something on screen 0's desktop that you wish to drag to a window on screen 1 ..... it's a trivial thing to change in the code (RootWidget::toggleDashboard() in kdebase/workspace/plasma/plasma/rootwidget.coo) i'm just not sure it's what we want plasma to be doing. anyone on panel-devel with some additional input? p.s. to Mike, the reporter: the component is plasma, not kicker. kicker is not part of kde4. If its easy enough then maybe we could have it as an option? No idea how it ended up in kicker, sorry > we could have it as an option
i'm trying to only provide options for things that actually make sense rather than use it as an excuse to ever make any decisions =) it's a fine balance, i agree. i didn't just close this report out of hand out of recognition of the fact that plasma is still searching for exactly where this balance point is, and this is squarely in the grey area.
a better understanding of actual use cases, in practice, over time will probably help determine the fate of this report.
No problems, I am fine to leave it as is and see what you have in mind :) |