The process followed under the hood to save the project files has been modified in v7.10 to minimize if not eliminate the risk of project file corruption.
The auto-save feature at regular intervals has been disabled until further notice to eliminate the risk of data modification using the UI at the same time that a background save is occurring. This has been reported as a potential cause of project file corruption.
When requested to save the project file, flow5 will
- Check that write access is given by the OS to write to the destination path, and if not will return with a message.
- Write the project file with the extension ".bak" to the temporary directory defined in the preferences; if this directory does not exist or does not have write access, flow5 will use the system's temporary directory.
If successful, flow5 will send a request to the OS to copy the temporary ".bak" file to the specified ".fl5" file. This operation will be an overwrite if the .fl5 file exists.
Unless an error message is returned, flow5 will send a request to the OS to remove the ".bak" file.
The goals are that
Back to top
- if the save process fails at step 2, the .fl5 project file will not have been modified.
- if the copy process fails at step 3, the .bak project file can be recovered by changing its extension to .fl5.