Page 1 of 1
TOAW III Equipment Editor
Posted: Thu Nov 05, 2009 5:04 pm
by parmenio
I'm currently in the process of writing a new Equipment Database Editor.
One of the gotchas in the current BioEd is that fact that unless you click on the "Update" button, any changes made to the currently selected item will be lost.
So the question is...
...is it preferable to automatically save the changes (i.e. to the underlying database in memory and not the the hard disk) or to prompt to save when navigating away from the item?
RE: TOAW III Equipment Editor
Posted: Thu Nov 05, 2009 5:33 pm
by vahauser
ORIGINAL: parmenio
I'm currently in the process of writing a new Equipment Database Editor.
One of the gotchas in the current BioEd is that fact that unless you click on the "Update" button, any changes made to the currently selected item will be lost.
So the question is...
...is it preferable to automatically save the changes (i.e. to the underlying database in memory and not the the hard disk) or to prompt to save when navigating away from the item?
Prompt to save. No automatic save (bad).
RE: TOAW III Equipment Editor
Posted: Thu Nov 05, 2009 6:54 pm
by noxious
ORIGINAL: vahauser
Prompt to save. No automatic save (bad).
Unless the autosave is in a distinct file (autosave.eqp for example), bonus feature : automatic backup of original file upon opening/import.
If you can store the project as its own DB in the format used by your editor, could be interesting to keep a form of revision history.
Cheers !
RE: TOAW III Equipment Editor
Posted: Thu Nov 05, 2009 7:12 pm
by parmenio
ORIGINAL: noxious
Unless the autosave is in a distinct file (autosave.eqp for example), bonus feature : automatic backup of original file upon opening/import.
To be absolutely clear, the autosave I had in mind is only to the
memory copy - saving the original file is a separate and distinct action.