Bug 401795

Summary:	Save Incremental Backup has wrong Modified Date
Product:	[Applications] krita	Reporter:	Kenneth Evans <ken>
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	halla, info
Priority:	NOR
Version First Reported In:	4.1.5
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Kenneth Evans 2018-12-05 19:58:19 UTC

SUMMARY
Save Incremental Backup (F4) does not have the correct modified date.  I am not sure what it is using, but it is different from the Created and Accessed dates, which are the current time.  I just did an incremental backup, and it has a Modified Date of yesterday, in fact.  Very confusing and seems wrong. It makes it difficult to determine which backup I am looking for.

Yes, I can apparently look at the Creation date, now that I know, but Windows typically uses the Date modified in Explorer, so that was not obvious and is not convenient.  And it's hard to see how a Modified Date that is not at the time it was saved is correct.

STEPS TO REPRODUCE
1. Work on a drawing.
2. F4
3. 

OBSERVED RESULT
Modified date is in the past.

EXPECTED RESULT
Modified date is when I saved it.

Comment 1 David REVOY 2018-12-05 20:08:52 UTC

It is probably a Windows version specific bug; I tested here on Linux appimage and git~master and I can't reproduce.

Comment 2 Halla Rempt 2019-02-25 12:42:40 UTC

Save incremental backup copies the file as it was when it was loaded to a new name; whether or not copying a file does change the modification date is OS dependent. 

In any case, Krita isn't setting those file attributes itself, so this cannot be a bug in Krita.

Comment 3 Kenneth Evans 2019-02-25 16:12:27 UTC

What a surprise! Who would ever think incremental backup was backing up with some state from the past.  I don't know of anything else that works that way, and it certainly isn't what I want or thought I was getting.  I want to save a snapshot of my work and continue working on the same file.

I can only speak for myself, but it's really hard for me to see why anyone would want it to work as it does.

And there is no option do do what I want, save a snapshot and continue working on the same file.

The documentation says:

Save incremental version
Save as a new version of the same file with a number attached.

Save incremental Backup
Make a backup file without leaving the working file.

If you insist on the incremental backup not being a backup of your current work, then please make it clear in the documentation what it is doing.

Based on past experience and your reaction here, I don't expect you will fix it, but it really is a gotcha and SHOULD be fixed.

(This is the same issue as #404782.)