I'm working with a large image on a network drive. Autosave is causing minute-long freezeups since saving to the NAS takes a while. Can the save process be done in the background so work isn't interrupted? Failing that, I'd prefer an option somewhere to choose where autosaves are located, so I could point it at a local drive. I can disable autosaves, of course, but I do like the feature. Reproducible: Always
Hi, Due to decade-old decisions this isn't easy to implement, I'm afraid. But it's not just important for saving over network drivers.
Git commit 189daca58291cf6d3443fdc53eac6d579c66086e by Boudewijn Rempt. Committed on 16/08/2016 at 13:46. Pushed by rempt into branch 'video-export-rebased'. Save to a temporary file, then copy the result over on success I thought we were already doing this, but apparently that only was done for remote urls, back in the days we still supported that. The temporary file is saved in the tmp dir, and then copied over. We even make a safety copy of the original file if it exists before doing the copy. This should make saving over network drives faster and more reliable, as well as saving in general more robust. Related: bug 366765, bug 357132 M +63 -17 libs/ui/KisDocument.cpp http://commits.kde.org/krita/189daca58291cf6d3443fdc53eac6d579c66086e
Git commit 3f138209f96cc34a72a135e440609e45633e4ae7 by Boudewijn Rempt. Committed on 16/08/2016 at 13:51. Pushed by rempt into branch 'master'. Save to a temporary file, then copy the result over on success I thought we were already doing this, but apparently that only was done for remote urls, back in the days we still supported that. The temporary file is saved in the tmp dir, and then copied over. We even make a safety copy of the original file if it exists before doing the copy. This should make saving over network drives faster and more reliable, as well as saving in general more robust. Related: bug 366765, bug 357132 M +63 -17 libs/ui/KisDocument.cpp http://commits.kde.org/krita/3f138209f96cc34a72a135e440609e45633e4ae7