No Save when closing a document ??

[mopperle]

I'm just starting to use Affinity Photo 2. And I experienced something I cant believe:

I open a RAW file and start editing it. Then I accidentally press "close document" and the document closes without asking me to save my work, no warning, nothing. Same happens, when I just close the App. Can this really be or did I miss a setting?

When I first click on "Develop" and then click on "close document, I'm asked to save it.

Happens with AP 2.2.1 on latest Win11

EDIT: I do not see this strange behaviour in APub

Edited November 25, 2023 by mopperle

[walt.farrell]

20 minutes ago, mopperle said:

EDIT: I do not see this strange behaviour in APub

Welcome to the Serif Affinity forums.

You wouldn't see this in Publisher, as Publisher does not have the Develop Persona.

This behavior is new in V2, and I think it's a bug. But I don't see a report of this specific behavior so I'm not sure.

[mopperle]

Thanks Walt, I searched for this, but didnt find anything.

So I'll open a bug report.

Regards
Otto

[R C-R]

3 hours ago, walt.farrell said:

This behavior is new in V2, and I think it's a bug.

Maybe I misunderstood something about this but when I open for instance a Nikon .nef file in AP V2.2.1 (which of course opens it into the Develop Persona) & then try to close it, I get the expected notification:

It doesn't matter if I do any editing on it while in that persona or not.

Maybe this is a Windows only bug?

[walt.farrell]

26 minutes ago, R C-R said:

Maybe this is a Windows only bug?

Perhaps.

[R C-R]

6 minutes ago, walt.farrell said:

Perhaps.

So you can duplicate the behavior on your Windows version? Have you tried it on your MBA?

[Komatös]

I can confirm that Affinity Photo quits immediately without warning if the close button is pressed.
 

[R C-R]

3 minutes ago, Komatös said:

I can confirm that Affinity Photo quits immediately without warning if the close button is pressed.

That sounds like it might be a different behavior than @mopperle reported, unless in that first post "document closes without asking me to save my work" means the app quits, not just that the document window closes while the app is still running.

[Old Bruce]

On my Mac If I use the the Red Close button whilst in the Develop Persona after opening a raw file and doing some editing the entire Consolidated window will close without any notification. Perhaps the Windows users are using the X in the upper right.

[R C-R]

5 minutes ago, Old Bruce said:

On my Mac If I use the the Red Close button whilst in the Develop Persona after opening a raw file and doing some editing the entire Consolidated window will close without any notification.

OK, I get the same thing when doing that but AP does not quit or crash. Same for you?

[Old Bruce]

1 minute ago, R C-R said:

AP does not quit or crash. Same for you?

Yes, it remains open, running. I can make new documents or open documents etc.

[mopperle]

Just to make it clear: When I click on the "X" (tooltip says "Close document") the document closes without saving/warning, but the app is still running.

When closing the app via File/Exit or via the X in the window title bar with a document still being open, also no saving/warning.

Btw, I created a bug report, so we may proceed there:

 

Edited November 26, 2023 by mopperle

[Old Bruce]

8 minutes ago, mopperle said:

Btw, I created a bug report, so we may proceed there:

In that report you should mention that this is windows and that you are clicking on the X.

[R C-R]

9 minutes ago, mopperle said:

Just to make it clear: When I click on the "X" (tooltip says "Close document") the document closes without saving/warning, but the app is still running.

So apparently different behavior than @Komatös reported....

[mopperle]

17 minutes ago, R C-R said:

So apparently different behavior than @Komatös reported....

Depends on which close button he is talking about:

- clicking on (1) closes ONLY the document window (as the tooltip says) without saving/warning, app is still open and running normal

- clicking on (2) or (3) closes the document AND the app without saving warning

[Komatös]

1 hour ago, mopperle said:

Depends on which close button he is talking about:

- clicking on (1) closes ONLY the document window (as the tooltip says) without saving/warning, app is still open and running normal

- clicking on (2) or (3) closes the document AND the app without saving warning

OK, I can confirm 1, 2 and 3.

Clicking on the close button of the document window has the same effect as clicking on the cancel button, except that there is no prompt.
This behavior is possibly 'by design'.
A scenario to get you thinking: If you open several RAW files at once and realize that you don't want to edit some of them after all.
In this case, it saves time that you don't have to click Cancel and go through the confirmation dialog. 

But maybe one of the Serif moderators or one of the developers here can clarify.
 

[mopperle]

Cant believe that, would call it a design flaw. It would be far away from any design rules.

[AlainP]

Same here, clicking "x" or File - Close closes the file without any warning. And as mentioned, if you first click the "Develop" button at the top left, it then ask to save before closing. So I'm not sure of the "by design"...

[Komatös]

17 hours ago, AlainP said:

Same here, clicking "x" or File - Close closes the file without any warning. And as mentioned, if you first click the "Develop" button at the top left, it then ask to save before closing. So I'm not sure of the "by design"...

Question: What happens if you load a .jpg or whatever image format and you don't make any changes to it and then click on the close button of the image file...? Exactly, it is closed without confirmation.

[walt.farrell]

7 minutes ago, Komatös said:

Question: What happens if you load a .jpg or whatever image format and you don't make any changes to it and then click on the close button of the image file...? Exactly, it is closed without confirmation.

But if you make changes to it, you are prompted to save.

Now, open a RAW file, and in the Develop Persona, make some changes. Now Close. If you are not prompted, how is that different from your example of a .jpg file. The user is still losing work. They are not losing any images (as the RAW file is still there in their file system), but they may have spent 15 minutes, 1/2 hour, or longer getting the image to look like they want it to in the Develop Persona, and then it's gone because they clicked the wrong button and weren't prompted to Save.

[AlainP]

Yes it's the same when you don't make any change. But here I edited the RAW file so it should ask if I want to cancel the modifications I made before closing. If you click on the "Develop" button at the to left it then will ask you before closing the file. 

When opening a JPG file and edit something in it, It then does ask if I want to save my changes before closing. It should be the same with the RAW file.

If you open a RAW file in Designer it will ask your if you want to save your changes before closing, even if you don't edit it, as it applies some curves before displaying it. Photo does not.

[mopperle]

1 hour ago, AlainP said:

When opening a JPG file and edit something in it, It then does ask if I want to save my changes before closing. It should be the same with the RAW file.

Indeed, unbelievable.
According to an answer from @Callum in my bugreport, this is by design. IMHO an absolute NoGo and a serious design flaw.

 

 

[AlainP]

It does not make sense at all. All other apps ask before closing when you've done some edit on the file. Even Designer ask before closing any file if you did some kind of edit. 

Photo does not ask unless you clicked on "Develop" .... no way it should work like this. It's a programming error easy to fix.

[R C-R]

1 minute ago, AlainP said:

It's a programming error easy to fix.

Apparently not a programming error because they designed it to work that way, but it is not a good design decision & should be fixed ASAP!

[PaulEC]

The thing is that until you develop the file, you haven't actually made any changes to it, that's why there is no prompt to save it; because you haven't made any changes until it is developed!

(Having said that, as it's quite possible to spend a long time adjusting the settings and then accidentally close the file before developing it, it would seem to make sense to have a confirmation dialogue, warning that the file has not been developed, rather than the file just closing.)