| Summary: | Allow to explicitly overwrite the original with versioning | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Frederic Grelot <fredericg_99> |
| Component: | Setup-ImageEditor | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | caulier.gilles, fredericg_99, trebor_x |
| Priority: | NOR | ||
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Frederic Grelot
2011-06-28 18:38:27 UTC
Disable Image Versionning (or tune it) in setup dialog and all must be fine. Gilles Caulier I'll do that. But still, I think that it is not incompatible. In my case, the modification was just about rotating the image (which was not automatically rotated, strange by the way...), and thus I didn't want to keep the original image. If i use the "Save changes" instead of "Save change as new version" (I had both choices, so that was deliberate), even with versionning enabled, I think that the label is pretty clear and that the old name should be used... I think that versionning is a very good new feature, but sometimes (like in my case), one may want to overwrite the old picture regardless of the default preference... if you have a JPG image, and rotate it in the Image Editor, you have a lossy operation and an indication to preserve the original. Rotate it with jpeglossless, and it's not recorded in the history (which may be regarded as a lack of support in the plugin, but it's at least a lossless operation) See #271672 for a wish to, among other, keep the current version always with the original file name and store away the original and intermediates at a different filename >if you have a JPG image, and rotate it in the Image Editor, you have a lossy
>operation and an indication to preserve the original.
>Rotate it with jpeglossless, and it's not recorded in the history (which may be
>regarded as a lack of support in the plugin, but it's at least a lossless
>operation)
Well, what I found is that : if I use "Image/rotate/Left or right" in album view, it's ok, the file gets overwritten. But if I use the editor, I have no choice but to use the "Save change" button, and this actually creates a new file while I didn't want to, and I don't want to disable versionning : is there no easy way to actually force overwriting of the image?? File/Export, then select the original seems to be the only solution... I really think it's an-natural...
Same here. Sometimes I want to have one or more copies (e.g. when doing many different and large modifications). But often I want to do only a litle correction and don't need it saved as a new version. It's annoying to delete all the original images and to rename the new versions. Frederic, This file still valid using digiKam 2.4 ? Gilles Caulier Frederic, This file still valid with 2.9.0 ? Gilles Caulier this bug is valid for 2.9.0 New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. Frederic, This file still valid using last digiKam 5.0.0 ? Gilles Caulier This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release ? It available at this url : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier digiKam 5.5.0 is released officially https://download.kde.org/stable/digikam/ ...and new 5.6.0 pre-release as bundle is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Please check if this problem still reproducible with these versions. Thanks in advance Gilles Caulier digiKam 5.6.0 is now release and available as bundle for Linux, MacOS and Windows. Can you check if problem still exists with this version ? Thanks in advance Gilles Caulier Please update this entry from bugzilla with current 5.8.0 pre-release bundle to see if problem remain. https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ Gilles Caulier *** This bug has been marked as a duplicate of bug 271672 *** |