Hey, I have been testing Keepass with several clients and I have a couple feature requests from them:
Would it be more logical to save the database when creating it in Classic version, like the Professional version already does? This makes it much more obvious that the db is a file on the filesystem and prevents the "disappearance" of the db after first use without saving.
Would the it be logical to have the "save db when closing/locking" on by default to avoid loss of information by people who are used to mindlessly click through dialog windows?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
AFAICT, the only real difference in behavior between V1 and V2 when creating a database is that V2 asks for a name & location for the database file immediately, while V1 waits to ask until the actual save needs to be performed. The fact that V2 asks up front does not mean the file gets created at that time; the asking is only in preparation for the save operation that will most likely occur after you input your data for the new file.
I do agree that sometimes KeePass - with its ability to remember and automatically repoen the last used file - can make it easy for users to forget that there is a file involved that needs to be saved, but it seems to me that the standard Save / Discard / Cancel dialog should be enough to remind them.
Now, to your second point: Personally, I feel that "people who are used to mindlessly click[ing] through dialog windows" deserve whatever consequences those actions cause for them. When a dialog box appears, it's generally because something unusual has occurred that needs to be addressed by the user, so I would be against any default that feeds the erroneous assumption that these warnings are pointless nuisances.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey, I have been testing Keepass with several clients and I have a couple feature requests from them:
AFAICT, the only real difference in behavior between V1 and V2 when creating a database is that V2 asks for a name & location for the database file immediately, while V1 waits to ask until the actual save needs to be performed. The fact that V2 asks up front does not mean the file gets created at that time; the asking is only in preparation for the save operation that will most likely occur after you input your data for the new file.
I do agree that sometimes KeePass - with its ability to remember and automatically repoen the last used file - can make it easy for users to forget that there is a file involved that needs to be saved, but it seems to me that the standard Save / Discard / Cancel dialog should be enough to remind them.
Now, to your second point: Personally, I feel that "people who are used to mindlessly click[ing] through dialog windows" deserve whatever consequences those actions cause for them. When a dialog box appears, it's generally because something unusual has occurred that needs to be addressed by the user, so I would be against any default that feeds the erroneous assumption that these warnings are pointless nuisances.
A little training goes a long way IMO.
cheers, Paul