Summary: | Sometimes reordering is needed for batch rename to succeed | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Anton Lavrov <lavrov.anton> |
Component: | AdvancedRename-metadata | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | caulier.gilles, lavrov.anton |
Priority: | NOR | ||
Version: | 5.8.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Patch for reordering of rename operations |
Description
Anton Lavrov
2017-07-27 16:50:04 UTC
Created attachment 106896 [details]
Patch for reordering of rename operations
Attached a patch to support reordering of rename operations.
Two major changes here:
1. Now when checking conflicts with existing files before starting batch rename, Digikam takes into account renamed files. E.g. before following rename sequence was not allowed because Digikam checked that name 2.jpg exists before starting the rename:
2.jpg => 3.jpg
1.jpg => 2.jpg
Patched version will take into account that file 2.jpg will be already renamed to 3.jpg, so there will be no obstructions for renaming 1.jpg to 2.jpg, and will allow this scenario.
2. Digikam will do necessary reordering of rename operations - e.g. it will change this sequence:
1.jpg => 2.jpg
2.jpg => 3.jpg
to:
2.jpg => 3.jpg
1.jpg => 2.jpg
|