Post by Stefan on Apr 30, 2022 5:02:16 GMT -5
Hi George,
Would you consider changing the filename format of the crashSave files?
Quite often, my initial action is to reload the CrashSave file into SPFLIte and use DIFF to find what changes it contains.
SPFLite latches on to <filetype> of CrashSave which means a new profile is created and it also neutralises some of the DIFF options, like comments, etc.
I'm suggesting replacing the current format of
<filename>.<filetype>.<date>.<time>.CrashSave
with
<filename>.CrashSave.<date>.<time>.<filetype>
The file would still sort next to the original in any FILE-LIsts and any RENAME the user may wish to perform is still straight forward but doesn't need to be done BEFORE the file can be inspected.
Personally, I tend to just REPLACE the original file from the CRASHSAVE-version's edit tab if I'm happy with the content and the delete the Crashsave copy.
