Bug 152905

Summary:	Batch processes does not work properly if target directory is outside Album Library Path
Product:	[Applications] digikam	Reporter:	Giorgio Carlo Gili Tos <gionnyboss>
Component:	BatchQueueManager-Core	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	caulier.gilles
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	5.0.0
Sentry Crash Report:

Description Giorgio Carlo Gili Tos 2007-11-26 01:08:54 UTC

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.

Comment 1 Arnd Baecker 2007-11-26 07:53:57 UTC

Maybe one warning/note at the beginning would be ok, but just one.

Gilles, I am not sure where this bug should be put:
digikam/kipiinterface or kipiplugins/batchprocessimages or something else ?

Comment 2 caulier.gilles 2007-11-26 08:06:06 UTC

Arnd, 

Code to fix is :

http://websvn.kde.org/branches/extragear/kde3/libs/kipi-plugins/batchprocessimages/batchprocessimagesdialog.cpp?revision=738848&view=markup

Method slotProcessDone(), line 690...

Gilles

Comment 3 Arnd Baecker 2007-11-26 08:56:47 UTC

Gilles,

slotPorcessDone is called once for every file, right?
So can one distinguish that
  ok = m_interface->addImage( dest, errmsg );
returned `false` for the first time and then ignore any subsequent
`false` (but only if it is the same message!).
(Approaches like keeping a list of messages received so far and
selecting specific ones for just one-time notification  
seems very much like a hack and
any change in the message string will screw things. There must be a better
solution ...)

Comment 4 caulier.gilles 2007-11-26 09:38:05 UTC

>slotPorcessDone is called once for every file, right? 

yes.

>So can one distinguish that
>  ok = m_interface->addImage( dest, errmsg );
>returned `false` for the first time and then ignore any subsequent
>`false` (but only if it is the same message!).
>(Approaches like keeping a list of messages received so far and
>selecting specific ones for just one-time notification  
>seems very much like a hack and
>any change in the message string will screw things. There must be a better
>solution ...) 

The error message must be displayed on the console. No need to open a message box for that.

Gilles

Comment 5 Arnd Baecker 2007-11-26 09:44:23 UTC

Gilles, of course, that's an alternative
(though I have an unfinished bug report about digikam&Co
reporting just too much stuff on the konsole ... ;-)

Ok, so I will convert it into a Warning, output onto the konsole...

Comment 6 caulier.gilles 2008-12-08 09:36:09 UTC

Giorgio,

This file still valid using kipi-plugins 0.1.6 ?

Gilles Caulier

Comment 7 caulier.gilles 2015-05-19 09:21:38 UTC

Giorgio,

This file still valid using kipi-plugins 4.10.0 ?

Gilles Caulier

Comment 8 caulier.gilles 2015-06-29 17:52:38 UTC

New Kipiplugins 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

Comment 9 caulier.gilles 2015-07-04 10:11:25 UTC

BatchProcessImage is not maintained since a while and is obsolete now. It will
be removed with 5.0.0.

Use digiKam BQM instead...