Repeated Document Save Request

[peexel]

In version 2.6, I noticed that when switching from Affinity Designer 2 to Photo 2 to make a modification, it repeatedly asks to save the project. For example, when switching to Photo, it prompts you to save the project in Designer before transitioning to Photo. Similarly, once the modification is done in Photo, it requires you to save the project again before returning to Designer. As far as I remember, previous versions did not require saving the project every time. I am not sure if this behavior is intentional, but is there any way to disable it?

[GarryP]

Which OS, what’s the exact version number of the applications, and how are you “switching”?

I’ve just used “Edit in Designer” in Photo (both 2.6.0 on Windows) and I wasn’t asked about saving before the modified document was opened in Designer, nor the other way round.

[R C-R]

I am seeing the same thing as the OP in V2 for Mac if, for instance, I open a file in AD, then use Edit in Photo (no save request yet), & then switch back to AD via Edit in Designer.

Same thing if I open a document in AP & use Edit in Designer to open it in AD. No save request when I do that but as soon as I use Edit in Photo to return to AP, I get the save request.

So basically, it is the round trip that triggers it.

[GarryP]

I went through this process:

• Launch Designer;
• Create new document;
• Add Rectangle layer.
• Save document;
• Modify Rectangle fill;
• Edit in Photo (also launches Photo);
• Modify Rectangle fill and size;
• Edit in Designer;

...and at no point was saving mentioned (except when I did it deliberately).
Then modifying the Rectangle again and using Edit in Photo again didn’t cause a message to be given.

I don’t know if we are supposed to get a message asking for the document to be saved before switching so I can’t tell whether being asked about it is expected or not.

It might be nice to have an option (in Settings) where we can say whether we want it or not.

For any non-trivial document I generally save the document before switching because I’ve lost some documents that way, but that was a while ago and I don’t know if the process is much more ‘robust’ nowadays.

[jmwellborn]

Maybe it is a MAC thing, but for me, it isn't a round trip. It is all the time.  Each time I use EDIT IN (Photo, Designer, or Publisher) I have to Save first.  Even if I don't change or modify a thing, I get the message no matter which app I choose.  Publisher>Designer or Publisher>Photo;   Photo>Designer or Photo>Publisher;  Designer>Publisher or Designer>Photo.  A new wrinkle is that if I open a new document in Photo and place an Asset on the blank canvas, then select EDIT IN DESIGNER I click on the Save message and get a crash.  No recovery file available.  Tried it twice.  Happened twice.  I have the crash reports, in case anybody is interested.

 

[R C-R]

8 minutes ago, jmwellborn said:

Maybe it is a MAC thing, but for me, it isn't a round trip. It is all the time.  Each time I use EDIT IN (Photo, Designer, or Publisher) I have to Save first.

For me, sometimes it takes a round trip & sometimes not. It does not seem to have anything to do with if I have modified the file in any way or simply opened an existing file or even created a new new totally empty one.

For example, I created an empty file in AD, used Edit in Affinity Photo to switch to AP, then immediately used Edit in Affinity Designer & got this:

Moreover, when I did click Save to create this Untitled.afphoto file & then switched back to AD & once again switched back to AP, I once again got the 'needs to be saved' warning.

This is without making any changes to the file at all, so something is seriously screwed up somewhere in the latest V2Mac  versions.

[jmwellborn]

29 minutes ago, R C-R said:

For me, sometimes it takes a round trip & sometimes not. It does not seem to have anything to do with if I have modified the file in any way or simply opened an existing file or even created a new new totally empty one.

For example, I created an empty file in AD, used Edit in Affinity Photo to switch to AP, then immediately used Edit in Affinity Designer & got this:

Moreover, when I did click Save to create this Untitled.afphoto file & then switched back to AD & once again switched back to AP, I once again got the 'needs to be saved' warning.

This is without making any changes to the file at all, so something is seriously screwed up somewhere in the latest V2Mac  versions.

I think it may be possible that the developers decided that because there have been numerous occasions in the past where people have not saved their work, but have subsequently lost it when using EDIT IN (whichever) and then reported it on the Forums with a plea for a rescue from Serif, it would be more expedient to require a Save.  If it is a "be sure to eat your Wheaties" reminder, I predict that we will get used to it.🤔

[R C-R]

40 minutes ago, jmwellborn said:

I think it may be possible that the developers decided that because there have been numerous occasions in the past where people have not saved their work, but have subsequently lost it when using EDIT IN (whichever) and then reported it on the Forums with a plea for a rescue from Serif, it would be more expedient to require a Save.  If it is a "be sure to eat your Wheaties" reminder, I predict that we will get used to it.🤔

I thought about that too, but that does not explain the inconsistencies I see (sometimes round trip need, sometimes not) or in particular why I have to save a totally empty, no layer document just to switch from one app to the other. For the latter, there is nothing to lose.

Then too, this seems to be a Mac only issue.

[peexel]

 

Here I am, my operating system is a Mac.

I'll explain the process, which I believe is similar to one of your posts:

1. I create a new document in Affinity Designer (but I don't insert anything; the document is empty).

2. I switch to Photo, it opens the document, but it's empty. I then go back to Designer (it asks me to save the project), but in reality, I haven’t added anything to the artboard. I’m simply switching from Designer to Photo and then back to Designer without creating any content. So, what changes is it saving, and why do I have to save an empty document?

[peexel]

7 hours ago, R C-R said:

Ci ho pensato anch'io, ma questo non spiega le incongruenze che vedo (a volte è necessario un viaggio di andata e ritorno, a volte no) o in particolare perché devo salvare un documento completamente vuoto, senza livelli, solo per passare da un'app all'altra. Per quest'ultima, non c'è nulla da perdere.

Anche in questo caso, sembra che il problema riguardi solo i Mac.

Could the problem occur when switching, for example, from Photo to Designer, causing the program to crash? Doesn't Affinity have an autosave feature? If it crashes upon opening, it should display the project recovery option! In the settings, you can enable autosave every 30 seconds, which is such a short amount of time that I doubt anyone would enter Photo, make a modification in less than 30 seconds, and then experience a crash when switching back to Designer. At this point, the program should display a warning rather than enforcing a requirement. This warning could include a checkbox to disable it in the future. However, if the modification occurred in less than the time set in the autosave preferences, then in this case, it makes more sense to save the project because there wouldn't actually be a saved copy (considering that the recovery time might be significantly longer than 30 seconds).

[R C-R]

34 minutes ago, peexel said:

I switch to Photo, it opens the document, but it's empty. I then go back to Designer (it asks me to save the project), but in reality, I haven’t added anything to the artboard. I’m simply switching from Designer to Photo and then back to Designer without creating any content. So, what changes is it saving, and why do I have to save an empty document?

That is what I (often) see as well. I cannot think of any good reason for this so I assume it is a new bug ... & apparently only in the Mac versions.

[R C-R]

19 minutes ago, peexel said:

Could the problem occur when switching, for example, from Photo to Designer, causing the program to crash? Doesn't Affinity have an autosave feature?

That doesn't explain why a totally empty document can sometimes be switched from one to another app without the save warning popping up ... or why it does when switching back to the first one.