So, if Affinity needs continuous access, why it was no warning and I was allowed to do my work all along? And why it only happened when I tried to save? Also, on opening, there was a recovery dialog which helped me recover a part of my edits, but not all of them (which is weird also, why AF Photo won't save a temp recovery data when such situation happens).įrom all talks on this subject, I still see no reason for the following: And it didn't happen once, it was repetitive, at least 3 times it happened until I decided to write on this forum. I understand that, but what puzzles me is that I was able to work just fine all along and edit my work, until I decided to save. Keep in mind that Affinity needs read access to the file for as long as it is open - it is not just about saving/writing back to it.
Perhaps then making sure the connection is re-checked, or allowing the user to select the path to the file (in case Affinity can't automatically find it for some reason), and also if possible to save the modifications so they can be recovered. Most probably this wouldn't be the desired solution. there was a short intrerruption at some point and Affinity did not check C-R I understand your point with cached copies, indeed, too many variables and too many complications in too many scenarios. pCloud is "locking" the file while sending it to the cloud server, so Affinity "thought" it cannot be overwritten/saved.Ģ. So, the storage was available, but for some reason Affinity could not access it.ġ. My issue while saving on my pCloud virtual drive confirmed it: whilst Affinity Photo was NOT able to save, I had no problem opening the drive and interacting with the files there. If not, it should be simple enough to build that into the app. As for other brief interruptions, say those that last for no more than a second or two, I would be surprised if the app did not already have a built-in delay before deciding the connection was lost.
0 kommentar(er)
