https://bugs.kde.org/show_bug.cgi?id=158556
--- Comment #89 from Duncan <1i5t5.dun...@cox.net> --- (In reply to cherenz from comment #88) > Still a valid for wish for Plasma 5. Indeed. I don't have permissions, tho. With plasma5 there is, however, a partial workaround. While panels still aren't part of activities (why, I haven't the foggiest, other than obvious bugs, my greatest disappointment after the upgrade, as it sure seems obvious to me that different activities naturally need matching different panels to go with them)... In kwin5's window rules, it's now possible to set windows (including panel windows) to appear only on one activity, or to force them to appear on all activities. As such, it's now possible to setup two activities, one with panels and one without. Unfortunately, there's a number of limitations at the moment. The first and biggest limitation is that in plasma5, all panels have the same hard-coded window title (Plasma) and window class, and no window role at all. Thus, it's impossible to create a rule that applies to only one panel; the rule applies to all panels or none. As such, it's still impossible to have different panels for each activity, you're limited to either all panels available or none. The second limitation is that rule can force windows to a specific activity, or it can force them to all activities (the default for panels). There's no way to force windows to all activities *BUT* one. Thus, if you are already using multiple activities, you can't simply add an activity that doesn't have panels. You can have panels on only one activity, but you can't have panels on all activities BUT one, which would seem to be the common request here, unless of course you only have two activities, one with a rule forcing all panels to it, another one without panels. Taken together, these two limitations severely limit the usefulness of the window rules force-to-activity feature as it applies to panels, because (1) the rule can only apply to all panels, not just selected panels, and (2) the rule can force panels to one activity, but not all activities BUT one, so it's possible to have only one activity with panels, but impossible to have only one activity /without/ panels, unless there's only two activities, one with and one without. (Or just one activity, without, but that's easy, just delete all the panels.) Still, it's progress, and if that activity window rule eventually becomes a list of activities, so one can choose multiple activities for a window to appear on without forcing it to all activities, and if panels eventually either get settable titles or distinguishable window roles (IIRC in kde4, panels had roles like panel#1, panel#2, etc, so rules could apply to just one of them) once again, then it'll be possible to setup specific panels for specific activities, even if it has to be done manually via window rules. But simply having a button to manually hide and unhide panels, as kde3 did, remains a pretty basic request, far simpler than having to jump thru window rule hoops even if the latter does eventually become possible without the limitations that apply today. Meanwhile, I've not tried it (yet, I might...), but I believe it should be possible to script either wmctrl or xprop (or a combination of the two), to set either specific window roles or specific window titles, based on panel window position and class. Once that is done, it becomes possible to use normal kwin window rules to specify specific panels as the role or title will no longer match all panels, and kwin window rules can then be used to set them to a specific activity. One can then create additional panels, if desired, probably with a slightly different position or size so the script doesn't set the role/title on the wrong one, to set to other activities, and it should finally become possible doing that, to match up panels and activities, which would cure the problem a different way, by letting a user setup an activity without panels. Unfortunately, even if possible as I suspect it now is, that requires a user knowledgeable enough about scripting to actually do it, and of course the time for them to script up this extremely ugly hack for what /should/ be a simple part of the builtin plasma UI. -- You are receiving this mail because: You are watching all bug changes.
