https://bugs.kde.org/show_bug.cgi?id=396569
Heiko Becker <heire...@exherbo.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO |RESOLVED
Latest Commit| |https://commits.kde.org/kre
| |name/b721366896023bc7ca1294
| |fd8bfd955803fc6b8c
--- Comment #2 from Heiko Becker <heire...@exherbo.org> ---
Git commit b721366896023bc7ca1294fd8bfd955803fc6b8c by Heiko Becker.
Committed on 02/09/2019 at 06:01.
Pushed by heikobecker into branch 'master'.
Don't enable plugins with no chance to disable them
Admittedly I don't know the motivation behind the current situation,
but if an UI is provided to enable/disable plugins it seems a bit
inconsisten to hard enable some plugins with no possibility for the
user to disable them. This might even be confusing because users
might take the disabled checkbox (even though it's checked) as an
indication that the plugin can't be enabled.
To avoid this, have plugins enabled by default instead of always
enabled.
M +2 -2 src/datetimeplugin.h
M +1 -1 src/dirsortplugin.cpp
M +1 -1 src/dirsortplugin.h
M +2 -2 src/fileplugin.h
M +2 -2 src/increasecounterplugin.h
M +3 -3 src/krenamewindow.cpp
M +2 -2 src/permissionsplugin.h
M +2 -4 src/plugin.h
M +2 -2 src/scriptplugin.h
https://commits.kde.org/krename/b721366896023bc7ca1294fd8bfd955803fc6b8c
--
You are receiving this mail because:
You are watching all bug changes.
