https://bugs.kde.org/show_bug.cgi?id=429588

            Bug ID: 429588
           Summary: Window rules kcm needs a duplicate button
           Product: systemsettings
           Version: unspecified
          Platform: Other
                OS: Other
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: kcm_kwinrules
          Assignee: kwin-bugs-n...@kde.org
          Reporter: 1i5t5.dun...@cox.net
                CC: isma...@gmail.com, plasma-b...@kde.org
  Target Milestone: ---

So the last couple weeks I've been switching to wayland.  As a result I've
needed to create new window rules /almost/ duplicating many of my old X-based
window rules, except of course with new wayland-style org.kde.whatever window
classes.

Critically, while I've basically completed the switch now, wayland's now my
default and I've deleted many of the old X-based rules, at first I didn't want
to touch them as I wasn't yet sure qt/kde/plasma's wayland support was going to
be mature enough yet to default to wayland, so I was duplicating rules left and
right, adding wayland versions duplicating my X settings but with different
class settings.

For such a use-case the window-rules kcm seriously needs a duplicate button! 
With it, I'd have been able to press duplicate, load one of the copies, modify
the name to reflect wayland, hit detect to get the new class settings and
modify them a bit if necessary, and hit apply, all without losing and having to
recreate what the rules actually /did/ or their position in the rule stack.

Because that duplicate button isn't there, I had to create a new rule, hit
detect to get the new match settings, apply so as not to lose it, back out to
the rule list and move the new rule from the bottom into its position next to
the old rule, hit apply not to lose that, then repeatedly switch between the
two rules copying the settings from the old one to the new one until they
basically matched except for the differing class settings.

The lack of that duplicate button therefore made the process far more laborious
than it should have been.

(Of course it was made even worse due to bugs such as bug #429586, as I hadn't
yet discovered that there's a back button when the individual kcm is loaded
with kcmshell5, so I was having to click out of the rules kcm and back to to
get back to the rules list as I was doing it in kde system settings which
doesn't have that back button, but that's a different bug.)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to