[digikam] [Bug 382811] New: Sometimes reordering is needed for batch rename to succeed

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382811

            Bug ID: 382811
           Summary: Sometimes reordering is needed for batch rename to
                    succeed
           Product: digikam
           Version: 5.8.0
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: AdvancedRename
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

E.g. I want to rename files:

  1.jpg => 2.jpg                                                                
  2.jpg => 3.jpg                                                                

If rename operations are performed in this order, batch rename will fail at the
first step because file 2.jpg exists. However if Digikam changes order of
rename operations to:

  2.jpg => 3.jpg                                                                
  1.jpg => 2.jpg

then batch rename will succeed.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382811

Anton Lavrov <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Anton Lavrov <[hidden email]> ---
Created attachment 106896
  --> https://bugs.kde.org/attachment.cgi?id=106896&action=edit
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

--
You are receiving this mail because:
You are the assignee for the bug.