https://bugs.kde.org/show_bug.cgi?id=372763
--- Comment #3 from Matthias K. <matth...@kaehlcke.net> --- Indeed Digikam now doesn't allow to start batch rename if there are conflicts, but that doesn't really fix the workflow problem :( My current workaround (w/ v5.6.0) is: - create a sub-directory 'tmp' and move all photos to be renamed into it - select a limited number of photos - try to rename - in case of conflicts select the first N photos without conflicts and rename them - move the renamed photos up into the actual album directory - select a limited number of photos - try to rename - in case of conflicts select the first N photos without conflicts and rename them - manually rename the first photo since it has a conflict - move the renamed photos into the actual album directory - repeat until all photos have been renamed This is extremely cumbersome compared with the previous behavior. Please provide some kind of reasonable solution. -- You are receiving this mail because: You are watching all bug changes.
