Bug 299918 - Share Worflow settings from BQM with Image Editor about image versioning
Summary: Share Worflow settings from BQM with Image Editor about image versioning
Status: RESOLVED DUPLICATE of bug 349064
Alias: None
Product: digikam
Classification: Applications
Component: Database-Versioning (show other bugs)
Version: 2.5.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-13 06:08 UTC by Axel Krebs
Modified: 2023-05-20 21:44 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Krebs 2012-05-13 06:08:56 UTC
with non destructive image editing feature, digikam improved enormously.
For my opinon, the npn-destructive image editing feature is not used completely, but contains even more positive options than users can apply at the moment.

With an individual history for each picture, one needs building up versioning-systems like a chessboard pattern. Sometimes, one cannot forecast the results of a specific treatment in advance; instead, one is forced to apply series of slightly different parameter settings to find out the very best parameter combinations.  


Reproducible: Always

Steps to Reproduce:
1. in this digikam version 2.5, only the last (or selected version) of a pic is stored.

2. one should be able (with a checkbox, e.g.?), to store every image manipulation step between original and last step of a version

3. it should be possible to save certain manipulation steps (~´workflows´) as pre-defined user-individual template.
Actual Results:  
At this time, one needs to use non-destructive image editor with noting specific settings manually. Several different settings has to be testet individually. 
it is a lot of testing time to reproduce the same results agin

Expected Results:  
Change history should be saved in a per-pic-history
Comment 1 caulier.gilles 2015-06-12 14:54:03 UTC
*** Bug 349064 has been marked as a duplicate of this bug. ***
Comment 2 caulier.gilles 2015-06-21 13:29:13 UTC

*** This bug has been marked as a duplicate of bug 349064 ***