| Summary: | KControl Theme Manager provides no warning that changes are irrevocable | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | NEW --- | ||
| Severity: | minor | CC: | bugwatch, darrella, kb9vqf, keithwdaniels |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2969 | ||
|
Description
Darrell
2013-11-08 13:31:36 CST
Instead of saying "These changes are not reversible." which would scare new users, I would use something like this: The configuration changes made when a new theme is applied, will not be restored when you revert back to the original theme. To restore these settings you will have to do it manually one at a time or use a backup copy of ~/.trinity. This explains that the changes will be made and implies that it is fixable but with a bit of effort. Keith I just remembered a third way. How about this: The configuration changes made when applying a new theme are not restored when reverting to a previous theme. To avoid this result requires 1) saving the existing settings as a new theme, 2) manually configuring each setting one at a time, or 3) using a backup copy of the user's Trinity profile directory (normally $TDEHOME). Only the (potentially) changed configuration files should be backed up, as the ~/.trinity directory can contain hundreds of megabytes of image data, mailboxes, etc. > Only the (potentially) changed configuration files should be backed up
Makes sense.
Which config files are affected by modifying the theme? The six buttons at the bottom of the dialog provide only a vague clue.
My idea of a warning message was only temporary relief. Long term the dialog should provide a method to restore all previous settings. Doing that likely requires creating (temporary) *.bak files in the user's profile. :-)
>Which config files are affected by modifying the theme? The six buttons at the
>bottom of the dialog provide only a vague clue.
For future reference in case somebody adds a Restore feature, several times I tested changing the theme. Looks like the following files are candidates for being modified when applying a new theme:
.trinity/share/apps/kdesktop/IconPositions
.trinity/share/apps/tdedisplay/color-schemes/thememgr.kcsrc
.trinity/share/config/clock_panelapplet_..._rc
.trinity/share/config/kcminputrc
.trinity/share/config/kcmthememanagerrc
.trinity/share/config/kdeglobals
.trinity/share/config/kdesktoprc
.trinity/share/config/kickerrc
.trinity/share/config/konquerorrc
.trinity/share/config/twinrc
.trinity/share/config/uiserverrc
Notes:
.trinity/share/config/kcmthememanagerrc might not exist before applying a new theme.
Some files do not always change:
.trinity/share/apps/kdesktop/IconPositions
.trinity/share/config/kcminputrc
.trinity/share/config/kickerrc
.trinity/share/config/konquerorrc
.trinity/share/config/twinrc
.trinity/share/config/uiserverrc
Regardless, adding a Restore function would require saving backup copies of the top list of 11 files.
|