Overwrite warning for SAVE option

[Just_user]

I'm a novice in using Affinity Photo.

Earlier I've been using Photoshop, Photoshop Elements and Lightroom. An now I 'm trying to migrate to Affinity...

But 1 thing got me into trouble.
When I wanted to save just an open jpg file, I chose the "SAVE" option.

And after that, my source file was immediately overwritten - WITHOUT any warning.

Please - add an option that would prompt you to overwrite the existing file before saving. Let it be possible to enable or disable it - it does not matter.
The main thing is that the user is warned in advance ...

Thank.

Yours faithfully,
    Anatoly

 

P.S. excuse me for my english...

[Alfred]

1 hour ago, emmrecs01 said:

Post removed by writer.

Why not use ‘Options > Hide’ to hide your post so that no one (apart from moderators) can see it?

[markw]

Do you not get this window when hitting 'Save'?

[emmrecs01]

54 minutes ago, Alfred said:

Why not use ‘Options > Hide’ to hide your post so that no one (apart from moderators) can see it?

Thanks @Alfred.  I wasn't even aware of that option!  Now done.

[walt.farrell]

46 minutes ago, markw said:

Do you not get this window when hitting 'Save'?

You only get that if the document needs to be flattened before it can be saved. If all you've done is Crop, or Resize, or if you've already merged any adjustments, then it will just Save without warning.

[markw]

Ah, I see what you mean, although thinking about it, a lot of apps if not most, behave in this way, at least on Macs.
‘Save’ always overwrites the original without a warning message, Pixelmator and Preview apps both behaves this way, as dose Text edit, etc... and well pretty much every app I have.
So it’s not without president, at least on a Mac.

[walt.farrell]

It's pretty standard on Windows, too.

Of course, many Affinity users "know" that they have to use Export to save a JPG, and thus they expect that if you open a JPG, make some edits, and perform a Save they'll  get a .afphoto file and their original will not be changed.

That's not true, of course, if you start with a JPG, PNG, or TIFF file. But fewer people know that.

[Just_user]

Thanks for an answers.......

 

22 hours ago, markw said:

a lot of apps if not most, behave in this way

I do agree - it is so .

And I agree that experienced Affinity users are aware of this.
But the point is that a beginner can lose many important files during such an operation - until he gets used to not press the SAVE button.
And such newcomers and such losses will be enough ...
That’s why I am asking to prevent losses and not to “spoil the impression” of a good program. 🙂

[Andy.Orange]

Still waiting on this one. I understand the implications fully, but everyone, myself included, makes mistakes or forgets. Not having a warning is quite disconcerting. Software should work 'as expected' not 'as designed'.

The program is smart enough to know whether you are about to overwrite an .afphoto file, or a jpeg. So how about including a warning the 'first time' you press save for a jpeg/whatever, offering the choice to save to .afphoto or "It's OK I know what I'm doing" button. After that first save, the functionality of ctrl+s or clicking save reverts to normal behaviour.

Not having a warning that a file is about to be overwritten is probably the single thing that stops me recommending AP to friends and family. Non tech-savvy folk will almost certainly end up overwriting their originals.

[carl123]

12 minutes ago, Andy.Orange said:

Software should work 'as expected'

It does

 

12 minutes ago, Andy.Orange said:

So how about including a warning the 'first time' you press save for a jpeg/whatever, offering the choice to save to .afphoto or "It's OK I know what I'm doing" button.

That would get really annoying if all I was doing was opening a JPG file to resize or crop it, etc.

 

14 minutes ago, Andy.Orange said:

Not having a warning that a file is about to be overwritten is probably the single thing that stops me recommending AP to friends and family.

When opening an image, it is good practice to always duplicate the background layer (CTRL+J) before doing any edits. If you get into the habit of doing that you will always receive a prompt when first saving the file. Don't forget to let your friends and family know that as well.

[PaulEC]

36 minutes ago, Andy.Orange said:

Not having a warning that a file is about to be overwritten is probably the single thing that stops me recommending AP to friends and family.

Presumably it stops you recommending quite a few apps, as this is fairly standard behaviour! 😄

(Actually, I think I'd find it quite irritating if I had to confirm it every time I save any changes!)

 

36 minutes ago, Andy.Orange said:

Non tech-savvy folk will almost certainly end up overwriting their originals.

The simple solution is not to edit original files, always work on copies!

[iconoclast]

You can't really satisfy everyone. I remember a very hard discussion I had on a GIMP Forum some years ago, with a user who was really angry about that he couldn't overwrite his original JPEG-files by just pressing Ctrl+S. Even I told him that especially JPEGs loose quality with every saving. In GIMP, Saving and Exporting are strictly separated, and you can use "Save" only to save as XCF-file, which is GIMPs house-format, or different kinds of zipped files. So you are not really in danger to overwrite your source file. What is a good solution, I think. If you really want, you can over-export your source file. But it's not very likely that this happens by accident.

[Pšenda]

On 6/14/2020 at 7:34 PM, walt.farrell said:

That's not true, of course, if you start with a JPG, PNG, or TIFF file. But fewer people know that.

I think this is an unnecessary and for many users confusing and thus dangerous paradigm violation - Save / SaveAs = affinity files, Export = oteher files.
Feel free to enable this feature, because for many situations, saving JPEG / TIFF / PNG using Save is a significant and welcome simplification and speed of work, but let it require user permission in Preferences.

 

20 hours ago, PaulEC said:

Actually, I think I'd find it quite irritating if I had to confirm it every time I save any changes!

I know applications (for example Acrobat Reader) where confirmation of overwriting the original file is required only for the first time, then no longer.