SYNFACTION
-
Posts
4 -
Joined
-
Last visited
Everything posted by SYNFACTION
-
Problem if Mac is offline while opening Affinity Photo
SYNFACTION replied to SYNFACTION's topic in V2 Bugs found on macOS
However, if I am not able to go online for a short time or cannot establish a VPN connection to the company network, working with AD or AP is practically impossible. The only way I can get around this is to remember to empty the list of all recently opened files while I'm still in the company (i.e. connected to a network drive). You can imagine that I don't always think about it... I develop software myself and therefore make the following assumption: Since the new function in the Affinity apps to display previews of recently opened files, the attempt to access that furthermore not accessible files does take place every time when the app is started (and possibly during other actions, I guess). There is a timeout that is far too long or we have a no suitable error handling for this case. V1 of the apps did not show this behavior! In other words, please don't access previously opened files unless an user really want to work with them! -
About a minute. And not only starting the app causes this behavior. Every try to open a file form the "open file" dialog causes the same behavior.
-
This problem also occurs with the designer and the publisher: If you are initially connected to a work network and have worked with files from it and afterwards you are offline (i.e. have no access to the files), Affinity Photo takes a very, very long time to start or every attempt to open a file takes a lot of time before you can finally work. This is very, very annoying! I suspect that the way recently opened files are handled in the software is causing this behavior. In version 1.x there was no problem of that kind
-
If you are working in a network environment where you have files from shared folders open and then later want to work at home for example without having access to the network environment, the AD2 seems to try to access the network files when starting the application (I guess it has something to do with recently opened files). This attempt causes very long startup times for the application, which is very annoying. AD 1.0 did not have this problem