| Summary: | BQM renames files (adds «_1») even if renaming is disabled | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Mikhail Krasilnikov <m.krasilnikov> |
| Component: | AdvancedRename-BatchQueueManager | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin, simon.pfeifer |
| Priority: | NOR | ||
| Version: | 5.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/digikam/368a4475c7fb5f34e2bdfbc7fc3e24d231d838db | Version Fixed In: | 5.7.0 |
|
Description
Mikhail Krasilnikov
2017-08-19 16:35:53 UTC
Typically, Image versionning is enabled, and BQM use it in this case. Gilles Caulier Image versionning is disabled. It was the first I've check. 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 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 *** Bug 375024 has been marked as a duplicate of this bug. *** |