[Kde-imaging] [Bug 195106] Kipi should be able to lock photos in host application

Marcel Wiesweg marcel.wiesweg at gmx.de
Wed Jun 3 20:55:24 CEST 2009


--- Comment #2 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-06-03 20:55:14 ---
How do the affected KIPI plugins store their lists? As KUrls?
As KipiImageInfo?
Moving operations from within digikam can be tracked, the task can be informed
that a given url has been moved to another given place, and do the checks
As for deletion, IMO if a user deletes an image he does not want it to be
processed anymore, so it's ok to drop it.
For both cases signals can be made available within digikam. We could also
provide wrapper lists in digikam code. Of course there must be API on the KIPI
side. Dont know how to solve this.

As for locking the main view, I think that the plugin should get a list of the
affected images and store it itself instead of relying that the view remains
locked. I dont think that any task that is a background task should have the
power to restrain the user working in the main view.

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Kde-imaging mailing list