Bug 314921 - Windows: consider using %TEMP% for saving autosave files of unsaved files instead of the user home folder (%USERPROFILE%)
Summary: Windows: consider using %TEMP% for saving autosave files of unsaved files ins...
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: git master (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-11 18:11 UTC by Eiko Yumi
Modified: 2014-02-28 09:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eiko Yumi 2013-02-11 18:11:12 UTC
Build: Krita for Windows 2.6.8.4 Experimental

In the currently downloadable Windows build of Krita, unsaved new files have their autosave files saved in the user home directory. Shortcut path on Windows: %USERPROFILE%

This is not a very optimal solution because it gets quickly clogged up with autosave files which unlike on Linux systems (as they start with a comma), are not hidden. A better and more logical solution for autosave files for new, yet unsaved files would be using the user temporary file directory, which on Windows has the %TEMP% shortcut.

For files that have already been saved it makes sense to save autosave files in the directories where the working file is (although it would be nice to be able to decide the path where to put them in program options). However, when they still are unsaved, the %USERPROFILE% directory doesn't seem to be the best choice, considering that new paintings would be in that state for a just brief time, and if they're not supposed to be saved (for example for quick tests), then perhaps having one or more autosave files permanently laying on the OS drive might not be very desirable.

Reproducible: Always




OS: Windows 8 Professional 64 bit
Comment 1 Halla Rempt 2013-02-12 11:28:37 UTC
Yes, that should be possible to special case for Windows.
Comment 2 Halla Rempt 2013-06-24 08:31:56 UTC
Git commit e2ef2c6226428c5ec9b93981cb5002264f4673b5 by Boudewijn Rempt.
Committed on 24/06/2013 at 08:30.
Pushed by rempt into branch 'master'.

On Windows, save autosave files in a temp location

(Also see bug for rationale)

M  +7    -1    libs/main/KoDocument.cpp

http://commits.kde.org/calligra/e2ef2c6226428c5ec9b93981cb5002264f4673b5
Comment 3 Halla Rempt 2013-06-24 08:32:11 UTC
Git commit aef4e1c2399931f43ecfbe606d5d252f42908306 by Boudewijn Rempt.
Committed on 24/06/2013 at 08:30.
Pushed by rempt into branch 'calligra/2.7'.

On Windows, save autosave files in a temp location

(Also see bug for rationale)

M  +7    -1    libs/main/KoDocument.cpp

http://commits.kde.org/calligra/aef4e1c2399931f43ecfbe606d5d252f42908306
Comment 4 Halla Rempt 2014-02-28 09:39:47 UTC
Git commit 522859efabad642358eec3aa0d0667a265ba538e by Boudewijn Rempt.
Committed on 28/02/2014 at 09:39.
Pushed by rempt into branch 'master'.

On Windows, autosave files are in the temp path

M  +5    -1    libs/main/KoApplication.cpp

http://commits.kde.org/calligra/522859efabad642358eec3aa0d0667a265ba538e
Comment 5 Halla Rempt 2014-02-28 09:39:55 UTC
Git commit 53a821be85f970fa5124109e26280a3e1c6767e1 by Boudewijn Rempt.
Committed on 28/02/2014 at 09:39.
Pushed by rempt into branch 'calligra/2.8'.

On Windows, autosave files are in the temp path

M  +5    -1    libs/main/KoApplication.cpp

http://commits.kde.org/calligra/53a821be85f970fa5124109e26280a3e1c6767e1