| Summary: | "Save Changes" button same as "Save As New Version" Button | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | hardy.public |
| Component: | ImageEditor-Save | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | caulier.gilles, freisim93, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 5.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.0.0 | |
| Sentry Crash Report: | |||
|
Description
hardy.public
2017-08-19 18:46:28 UTC
That might not be the clearest of UI choices. I believe this is due to the how digikam is configured. In the editor configuration you can choose whether an edit should be done in place or as new version (didn't check this now though). Thanks Simon. Yes you're right. If I disable "Enable Non-Destructive Editing and Versioning" then I just get "Save" and "Save As" buttons which operate as you might expect. It looks like the "Save Changes" button may be redundant when "Non-Destructive..." is enabled. not redundant i think, but miss-spelled... But what does it do differently to "Save As New Version"? If i remember, one create a new version in original format, the other one use the versionning settings. Save changes, save a new version of the image, depending on the setting, the original image is now hidden. Save image as new version, save the image as a new branch, the original image is never hidden. No bug, I'm closing. Maik |