[Digikam-devel] [Bug 152905] New: Batch processes does not work properly if target directory is outside Album Library Path

[Giorgio Carlo Gili Tos]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=152905         
           Summary: Batch processes does not work properly if target
                    directory is outside Album Library Path
           Product: digikam
           Version: unspecified
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: gionnyboss gmail com


Version:           9.2 (using KDE KDE 3.5.8)
Installed from:    Fedora RPMs

If you try to do a batch process to images, you have to specify a target directory that is a subdirectory of the Album Library Path specified in Digikam settings. If you specify a target directory not inside the Album Library Path, Digikam does the work correctly, but after every image conversion an error dialog comes out with this message: "Error adding image to application; error message was: Target album is not in the album library."
It works anyways, but it is unacceptable to click "Continue" after every image conversion, especially if you have a lot of images to convert.
I think that you should be able to specify a target directory for processed images outside the Album Library Path, because it can happen that you need processed images just to do something with them and then you want to delete them, so there is no need that processed images are included in Digikam albums. For example, I would like to resize some images so that I can send them via email to friends, and then I want to delete images. And I don't want that smaller resized images are in a Digikam album.
I guess that this has been done for coherency in the application and this is not a big problem, I can live with it, but it is weird that it works anyways but this error still comes out. I guess that this is a bug, because if it works you should not see any error message.
I hope that my report can help you to improve this great application.