Version: (using KDE Devel) Installed from: Compiled sources quite honestly, the new stuff as a replacement for the old checkbox is a major usability regression. it's just too complicated for joe user ... i think a reasonable solution would be auto-generating a rule set when the checkbox is checked and deleting it again when it is unchecked. the rule set would have an indicator that it is an auto-generated one (to be easily recognizable in the editor) and a "dirty" indicator that would cause a warning to be issued if the checkbox is unchecked and the ruleset was edited. or maybe just remove the "auto-generated" indicator and uncheck the checkbox when the ruleset is edited.
*** Bug 85271 has been marked as a duplicate of this bug. ***
CVS commit by lunakl: #84605 - make the Alt+F3/Advanced/Special window settings option find automatically a match entry and create a new one if none is found. CCMAIL: 84605-done@bugs.kde.org A kcmkwin/kwinrules/kcm.cpp 1.1 [GPL (v2+) (wrong address)] A kcmkwin/kwinrules/kcm.h 1.1 [GPL (v2+) (wrong address)] M +83 -22 rules.cpp 1.27 M +7 -1 rules.h 1.19 M +13 -2 utils.cpp 2.8 M +14 -2 kcmkwin/kwinrules/Makefile.am 1.6 M +1 -0 kcmkwin/kwinrules/kwinsrc.cpp 1.2 M +153 -67 kcmkwin/kwinrules/main.cpp 1.6 M +0 -53 kcmkwin/kwinrules/main.h 1.3 M +15 -1 kcmkwin/kwinrules/ruleswidget.cpp 1.12 M +3 -1 kcmkwin/kwinrules/ruleswidget.h 1.5
hmm, i think it is still too complicated. the dialog asking what windows should be affected is ok, i assume, but that i _have_ to make the choice of the options to save myself is way too much. i think my idea above is quite good and it shouldn't be too hard to implement. btw, what are the "do not affect" settings good for - is some settings inheritance implemented?