Bug 383707 - BQM renames files (adds «_1») even if renaming is disabled
Summary: BQM renames files (adds «_1») even if renaming is disabled
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-BatchQueueManager (show other bugs)
Version: 5.6.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-19 16:35 UTC by Mikhail Krasilnikov
Modified: 2017-08-27 06:12 UTC (History)
3 users (show)

See Also:
Latest Commit: https://commits.kde.org/digikam/368a4475c7fb5f34e2bdfbc7fc3e24d231d838db
Version Fixed In: 5.7.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Krasilnikov 2017-08-19 16:35:53 UTC 
I'm using BQM to adjust time in photos. On «Rename» tab I've set to use original filename. But BQM adds «_1» suffix for all changed files.

And I'm not alone with this problem: https://forum.kde.org/viewtopic.php?f=19&t=135711
Comment 1 caulier.gilles 2017-08-19 20:50:43 UTC 
Typically, Image versionning is enabled, and BQM use it in this case.

Gilles Caulier
Comment 2 Mikhail Krasilnikov 2017-08-20 10:49:06 UTC 
Image versionning is disabled. It was the first I've check.
Comment 3 Maik Qualmann 2017-08-20 16:52:53 UTC 
The extension "_1" is here a counter so that the original image is not overwritten. Otherwise select in the BQM settings under behavior the automatic overwriting.

Maik
Comment 4 Maik Qualmann 2017-08-25 10:29:26 UTC 
Git commit 368a4475c7fb5f34e2bdfbc7fc3e24d231d838db by Maik Qualmann.
Committed on 25/08/2017 at 10:28.
Pushed by mqualmann into branch 'master'.

use round brackets for the new file counter, like as Dolphin to distinguish it from versioning
FIXED-IN: 5.7.0

M  +2    -1    NEWS
M  +1    -1    libs/threadimageio/dfileoperations.cpp

https://commits.kde.org/digikam/368a4475c7fb5f34e2bdfbc7fc3e24d231d838db
Comment 5 Maik Qualmann 2017-08-27 06:12:52 UTC 
*** Bug 375024 has been marked as a duplicate of this bug. ***