eobet Posted January 22, 2023 Share Posted January 22, 2023 What the absolute F? It's 2023? How is this an acceptable UX? At least when I when to recent files and opened it again, Designer told me that a recovery file existed and then I got back to where I was and was able to save it, but why did this have to happen at all? Quote Link to comment Share on other sites More sharing options...
debraspicher Posted January 22, 2023 Share Posted January 22, 2023 50 minutes ago, eobet said: What the absolute F? It's 2023? How is this an acceptable UX? At least when I when to recent files and opened it again, Designer told me that a recovery file existed and then I got back to where I was and was able to save it, but why did this have to happen at all? The "[ACCESS]" line, makes me wonder if that was a placeholder for additional text and that particular dialogue routine is unfinished. The NSA-esk force close is not cool. Patrick Connor 1 Quote Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted January 23, 2023 Staff Share Posted January 23, 2023 @François R, @N.P.M., @iuli, @NotMyFault I have hidden your posts. Please step away from this thread. @eobet Sorry about the argument that happened below your post, none of which was relevant or helpful. I will take action if this thread breaks down any further. 19 hours ago, eobet said: At least when I when to recent files and opened it again, Designer told me that a recovery file existed and then I got back to where I was and was able to save it, but why did this have to happen at all? That is not a message we have seen reported before, and the [ACCESS] message is just us reporting the error message that the operating system has given us. Sometimes those messages are useful to get to the bottom of the problem, but in this case it seems to just add to the uncertainty about what just happened. We cannot do anything to change the wording of the OS error, other than to display it in case it helps. Can you give us any more details about your system and network setup that would help us to help you? NotMyFault, François R and iuli 2 1 Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
carl123 Posted January 23, 2023 Share Posted January 23, 2023 @eobet Where were you opening that file from and saving to (if different) when the error occurred (Local drive, external drive, USB, NAS, cloud, etc It's similar to this one but slightly different Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
Tia Lapis Posted January 23, 2023 Share Posted January 23, 2023 If you are on macOS it sounds like you tried to save to a location where Affinity has not been allowed to write to. You could check this in the settings.app of macOS. Quote Mac mini M1 / Ryzen 5600H & RTX3050 mobile / iPad Pro 1st - all with latest non beta release of Affinity Link to comment Share on other sites More sharing options...
shushustorm Posted January 28, 2023 Share Posted January 28, 2023 I think I've seen something similar in V1 Designer on iPad when saving on local Files.app and choosing a different path than below /Designer. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.