chrisb wrote: ↑Thu Feb 22, 2018 7:16 pm
...
I open a commandline and list the backup files by date. Then I copy the most recent to the current file and check if it is ok. If not I repeat the last commandline and change just the number of the source file. I continue until I have found the correct file.
Having the obsolete timestamp in the filename would make this difficult because I have to type much more, and please consider, that this is in a situation where I am upset enough, because some of the work gets lost.
...
Have you a script to do that? With a script you can do almost as well and simpler. A restoreLast.bat or restorLast.sh would do it automatically, without sacrifying the archives as you do.
The file revert function could also be improved, adding a list when cliquing on revert with choices "revert to last" and the list of the archives available.
When a model is garbled because of software problem I copy and paste in a new document what works quite fine most of the time. For human mistakes it does not!
I would propose using placeholders like e.g. the path workbench does. There could be placeholders like
%p for the path, enabling the user to have the backup files in the same or in a dedicated directory
%d, %m, %y for day, month and year, enabling the user to control the date format
%f for the raw filename prefix, enabling to have the same backup file set for different files
%n for a number incremented one by one as we have it now,
That is not a big issue but needs to add parameters to the software. I am not ready to do yet as I do not know that part of the software.