DavorP wrote:
We are running windows.
Surely it would not be a huge issue to keep temp files in history for a number of days instead of overwriting on next run.
The 'temp' files (or autosave files) are constantly being updated depending on the data safety settings you have in the Work Environment.
In ultra safe mode it is tracking every step the user makes.
So these temp files are constantly being updated - not just on the next run.
Also they are not in a file format that can simply be opened.
A single project is split among many temp files and folders.
They exist until the user shuts down properly (or chooses not to save), when this happens the temp files should be cleared.
So even if you are constantly backing them up, you will now be backing up an empty temp folder.
I think this will be all too messy to keep multiple backups and try to restore them.
It is not simply a single file.
As mentioned by schagemann, the user should save every now and then.
This will create a backup (.BPN) file (again depending on your settings but it is doing this by default) everytime the user saves.
This .BPN file can simply be opened as a normal file or can be renamed as .PLN and opened.
This way you can potentially only lose the work done since the last save.
So if the user shuts down without saving, you have the current .PLN file that was last saved and the .BPN file is the file save the time before that.
All you will lose is the work since the last save - so it is much easier to just get the user to save often.
Barry.
One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11