The source project of this merge request has been removed.
Make "Save Incremental Version" update recently used files
Since several users (including myself) got confused when only the old file version shows in the history of recently used files after "Save Incremental Version", I changed the behavior.
In order to not flood the history with versioned entries of the same document, the old entry gets removed (if present) and the new version is added.
Do you think that only keeping the latest version is sensible? Or can you think of any edge cases that need special attention?
Test Plan
Use "File"->"Save Incremental Version" and verify that the old file entry (if present) gets removed and the new file version gets added, and that the rest of the history stays intact.
Formalities Checklist
-
I confirmed this builds. -
I confirmed Krita ran and the relevant functions work. -
I tested the relevant unit tests and can confirm they are not broken. (If not possible, don't hesitate to ask for help!) -
I made sure my commits build individually and have good descriptions as per KDE guidelines. -
I made sure my code conforms to the standards set in the HACKING file. -
I can confirm the code is licensed and attributed appropriately, and that unattributed code is mine, as per KDE Licensing Policy.