Feature #378
Improve warning of template overwriting solid file
| Status: | Closed | Start: | 10/25/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | Cambell Prince | % Done: | 100% |
|
| Category: | application | Spent time: | - | |
| Target version: | V0.11 | |||
| Resolution: | fixed |
Description
I'm using Solid 0.9.338.
There's a surprise when applying a new template: it persists even if the user later chooses not to save when exiting the program.
Because edits of the lexicon database persist only if saved, I expected that would apply to changes to the template as well, both for edits of the template and applying a different template.
I saw afterwards the message near the bottom of the <Choose SOLID Template...> dialog: "Click here to preserve the current Solid settings under a new name before using a new template". Although it has a warning icon, I wouldn't say it's worded as a warning because a user could still expect to back out of any template changes by not saving.
Because the saved status of template versus database is so different, I recommend that it be made explict somehow in the program.
At the very least, provide a popup warning message when the user attempts to load a new template. The warning would say that the current settings will be lost unless saved under a new name. (A popup is more effective than a warning on the dialog interface.)
Associated revisions
Fix #378: Improve warning of overwrite solid file
Fix #378: Further work on template chooser
History
Updated by Cambell Prince over 2 years ago
Well, I really don't like save buttons. I think they lead to all sorts of problems. The thing with solid is that there are really two distinct data files. The solid file, and the data that is being edited. I see the 'solid file' as being the domain that solid operates in, and the data is the users data. So, we've given a 'save button' for the user to choose to save their edits.
The apply template, is really saying throw away all my work, and over write it with a new default template. Just like applying a new template to a power point or a new template to a office document. I'm kind of keen on allowing folk to leave their data alone if they wish. In that sense the save button is meant for user data only. It's not meant to apply to the solid file at all. The solid file should be continually saved.
I remember we had quite a discussion in the office over the two different saves (one for solid file, one for user data). We didn't want two save buttons. So, before I changed what we've got, I'd want to make sure we were heading to something better. I don't think that having same save semantics is better. Then you get the question 'How do I save the solid file, but not my data?'
Anyway, it's food for thought. I get the message that you were surprised when your solid file was over-written by the new template.
Updated by Cambell Prince over 2 years ago
From Scott:
Thanks, Cambell. I agree it's best not to have two separate saves (database + Solid settings).
That being the case, I recommend the warning on the <Choose SOLID Template...> dialog be strengthened in two respects. (1) Make explicit that applying a different template will overwrite the existing one / the current settings will be lost unless saved under a new name. (2) Move the warning closer to the list box of templates.
Based on my experience, the current warning is easy to miss (small print, low on the dialog interface hence separated from the focal action area). And the wording allows the misinterpretation that one can back out of a change by not saving.
To say this another way, the user doesn't necessarily know the consequences and therefore needs to be told. Thanks for considering this.
Scott
Updated by Cambell Prince over 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r352.
Updated by Cambell Prince over 2 years ago
- Status changed from Resolved to Closed
- Resolution set to fixed
I've put the warning higher in the dialog and reworded it somewhat. Hope that helps.
Updated by Cambell Prince over 2 years ago
Fix available in 0.11.345
Updated by Cambell Prince over 2 years ago
Improved fix available in 0.11.347