[digikam] [Bug 372763] New: Rename does not give options on Conflict

[bugzilla_noreply]

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

            Bug ID: 372763
           Summary: Rename does not give options on Conflict
           Product: digikam
           Version: 5.3.0
          Platform: Mint (Ubuntu based)
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: AdvancedRename
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

When renaming a number of pictures, if there is a name conflict it displays an
error message and gives the option to abort but no option to choose a different
name.  DK4 gave that option and also suggested a new name.

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

[bugzilla_noreply]

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

Matthias K. <[hidden email]> changed:

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

--- Comment #1 from Matthias K. <[hidden email]> ---
I'm also experiencing this problem. This is a major issue, since the renaming
process stalls once it encounters a conflict, thus batch renaming is broken if
the batch has conflicts :(

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

[bugzilla_noreply]

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

Anton Lavrov <[hidden email]> changed:

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

--- Comment #2 from Anton Lavrov <[hidden email]> ---
This issue with non-atomic batch rename was fixed in 5.5 (or maybe earlier) -
now Digikam checks for conflicts with existing files and doesn't allow to start
batch rename if there are conflict.

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