Auto-Backup for JPGlossless cropping

[helmut]

As written in topic Lossless JPG editing, JPGlossless cropping is lossless for the area within the selection, but the user will loose all of the non-selected area. This cannot be undone.

So using the function "JPGlossless cropping" is pretty cumbersome and even dangerous:
- Users are endangered to destroy their images.
- Users first have to make a backup of their image and then apply JPG cropping.

I'm aware that there is a warning dialog which tells the user that JPGlossless transformations directly affect the image file. But users might have even switched off the warning dialog because they kept using JPG lossless rotation, which is lossless and can be used without problems.

I suggest to add something like an "auto-backup" or something else which avoids the danger of loosing an image. Perhaps this auto-backup can be also applied whenever saving an image with the same name.

That's just a first idea for a perhaps larger functionality. Suggestions and ideas are welcome (as always).

[Dreamer]

Yes, I don't know how, but should be implemented, I think it's very important feature - it should work as Undo if possible, check also these suggestions:

http://newsgroup.xnview.com/viewtopic.php?t=4267
http://newsgroup.xnview.com/viewtopic.php?t=3819

[oops66]

Yes, I don't know how, but should be implemented, I think it's very important feature - it should work as Undo if possible, check also these suggestions:
http://newsgroup.xnview.com/viewtopic.php?t=4267
http://newsgroup.xnview.com/viewtopic.php?t=3819

Yes, like here (for the 1.92 beta) for the Undo-Redo function :
http://newsgroup.xnview.com/viewtopic.php?t=13970
.....
But the first image (the original one) must always stay in Tmp memory (as soon as we apply a first or more changes¦effects) even if the number of modifications is over the level in the xnview.ini file: Undocount= setting.

By this way, undo all changes always means : return to the first step (the original image).

[marsh]

I'm aware that there is a warning dialog which tells the user that JPGlossless transformations directly affect the image file. But users might have even switched off the warning dialog because they kept using JPG lossless rotation, which is lossless and can be used without problems.

Good point. Should there be seperate warning for rotate and crop?

[helmut]

I'm aware that there is a warning dialog which tells the user that JPGlossless transformations directly affect the image file. But users might have even switched off the warning dialog because they kept using JPG lossless rotation, which is lossless and can be used without problems.

Good point. Should there be seperate warning for rotate and crop?

Good idea. Separate warnings are a possible (interim?) solution.

[Dreamer]

Good idea. Separate warnings are a possible (interim?) solution.

I agree. Undo would be the best solution, of course.

I'll add this topic to the Global Request & Suggestion list, because it's very important.

[XnTriq]

One interesting observation I've made when applying lossless transformations to write-protected JPEGs is that a new cropped/rotated copy is created, since the original file can't be overwritten:

An error occurs, maybe original file is in READ only.

• original.jpg » original.jp_
  original.jpeg » original.jpe_

This goes for both Browser and View mode.

[marsh]

Good idea. Separate warnings are a possible (interim?) solution.

I agree. Undo would be the best solution, of course.

v.1.92 now has seperate warnings for jpeg crop and rotate.