Search the Community
Showing results for tags 'afp-1316'.
Found 3 results
I am working directly on the network. When PC goes to sleep with a file opened, then after wake up, the file cannot be saved anymore. An error appears that the file access was lost and the document has to be closed now, resulting in loss of all work since last save before sleep. This is unacceptable and the only program I know of not handling this correctly. When the file path gets lost for any reason (network lost, USB drive disconnected, etc) the resolution cannot be to close the document with all changes unsaved! The normal and usual behavior is to provide the "Save as..." dialog to give the user the chance to save the current state elsewhere. This is the minimum requirement. Actually I would expect that Affinity can properly handle the particular situation I described above, ie not throwing up an error after wake up at all. Facts: Windows 10 (latest build), Affinity Designer (I do not have Photo; latest build)
Hi, I have noticed an error while saving files opened from SMB shares with Publisher Mac. It happens only when opening the file for the first time and trying to save it (save command or save as with the same name). When the file is reopened then it saves normally. Save as with different name also works fine. I have the the same issue with Af Designer and Photo apps since version 1.6. Had no issue with versions 1.5. Could you please investigate the error? I checked it on 2 different Macs and 2 different SMBs (WD and Synology). Thanks
Hi, I often work from home. When I do, I let my labtop hibernate, take it with me, and resume working using VPN from home. Problem is: Affinity detects that file handles are no longer identical to the ones before switching networks, and the error handling is quite punishing: The application behaves exactly as the message suggests: The unsaved document is being closed, even if it is still in memory and the path to the file is still valid. All changes since last (auto-)save lost. I know that my use-case is probably rare, but the error handling here is not ideal. At least let me save the document to a local drive and don't close it, while it is still safe and sound in memory. Regards, Chris