forest-for-trees

@MikeTO Thanks for the visual. I did exactly as you suggested, unchecking the Command+` checkbox, then restoring defaults, and then restarted my computer. Still no dice. I also checked to see that my modifiers are also set to defaults, see attached screenshots of both (dark theme flipped on right as I was taking the second). It's driving me mad, because I much prefer the Command+` shortcut to Control+`. Such a small thing, but you really notice it when it's not working as expected. Thanks for all your help, I'll definitely try any other suggestion you might have. @nwhit Thanks for confirming, such a mystery!

@MikeTO Cmd+Tab still works to change applications. That's so strange that Cmd+` is still working for you in Ventura, I'm on system settings here. I've restarted my system plenty of times, and no change. This is across applications, same thing in Safari, so in hindsight I don't think Affinity configuration is going to affect this. What's weirder is that Control+` is now working to switch between tabs within applications. I use Cmd+] primarily to switch tabs in Safari so I never noticed it there. Are you also running Ventura 13.3.1 (a)? Thanks.

@thomaso That works for me! So glad to have that function back. They must have changed this in a recent version of MacOS. Thanks again! @MikeTO The standard US keyboard, I haven't customized anything about the keyboard for my new computer. I also hadn't customized the shortcuts, but trying to reset didn't solve the problem. It seems that Apple may have just changed something in recent versions of MacOS and now it's Control + tab. I can live with that.

@thomaso Thanks for sharing. Command + tab is different from command + tilde, at least it used to be. So strange that MacOS doesn't have anything set for that shortcut, I've been using it for years in various apps. Now it seems not to work anywhere. Maybe not a problem with Affinity, but I don't believe Affinity has any way to configure "Toggle document" keyboard shortcut. It would have to appear in the menus, but I don't think it does? @walt.farrell I'm also curious! Where can we find that setting?

When I started using Affinity designer 3 years ago, I was able to toggle between documents with cmd + ~, as is common in applications on MacOS. However, recently (perhaps after installing a MacOS update?), cmd + ~ no longer does anything. I don't see a menu option to toggle documents, so I don't know how to configure the hotkey to work again. I am using MacOS Ventura 13.3.1 (a) on a 2021 14" MacBook Pro. Any ideas are appreciated!

Affinity Designer just crashed on me 3 times while trying to save a file. This is getting pretty silly. This issue has been open for almost a year, and you can't give us any progress update despite new feature and product launches? Especially frustrated that I bought the latest version of the Affinity suite praying almost entirely that it fixed this single bug. I don't care at all about the rest of the stuff you guys released, it's completely unimportant. You should always fix the bugs first. This has to be affecting a ton of users, honestly who isn't using a remote file manager like Dropbox these days? I log my reports every single time, I have to imagine the developers are just ignoring them. Can you please, please give us an update on when this bug will be fixed. It's seriously so annoying and wastes like 5 minutes every time I want to save a file, which is ALL THE TIME.

I just bought version 2 of designer. I was praying that this bug would be fixed, but nope! It's still alive and just as annoying as ever! This issue seriously impacts my workflow and has for the last 6+ months. Is there any update on a fix for this problem? Affinity's apps are the only ones on my computer that have this type of problem...

Hi @Dan Cthanks for the update. So do you think simply clicking export to open a Finder window inside of a cloud drive could cause the problem? It is occurring for me as soon as Finder opens and before I even select a location to export. But it only occurs sometimes and regardless of whether those files are synced locally.

Hi @Dan C Any update on this? It affects me all the time before I even select a directory, so I don't think it has anything to do with Dropbox. I often have to restart Affinity twice or more before I'm able to export anything and I export things many, many times every day . It only started happening after an upgrade to the latest version of MacOS. Look forward to hearing your news.

Hi @Dan C, Thanks for detailed instructions and for your continued help in diagnosing the issue. I didn't see a "User Reports" category, but I did find Affinity logs under the "Diagnostic Reports" section in the Console app. See attached latest log. I can attach earlier ones as well if useful. All due respect, the workflow you're suggesting of first exporting to local directories, then copying to cloud synced directories is not realistic for me. I pretty much _only_ save documents to cloud synced directories, especially files of this type which I want a full history of. And I export a lot of files from Affinity. Adding this extra step would be such a headache, that I would rather deal with the crashes than do what you're suggesting. I think that given the direction of computing towards the cloud, it's not reasonable to expect people to do this. And given that Finder doesn't crash on me, this must be something that Affinity can fix if it is related to the problem. Understood re: save/auto save suggestions. Affinity Designer_2022-07-13-131140_Jordans-MacBook-Pro.diag

Hi @Dan C, Just experienced another crash. I was trying to export 4 files with .png filetype at 2x scaling. See attached screenshots. The crash report is massive at 41131 lines of text, so I won't burden the thread with that, but I have saved it to a file in case you have specific questions. Thanks in advance.

Hi @Dan C, Thanks for the quick reply. 1. I'm not sure, I haven't noticed a specific file type being problematic. I usually export either .png, .jpg, or .svg. As far as I know, it happens with all 3 file types. 2. Affinity store 3. There is no error message. The app hangs ("The application is not responding") when I click the export button. After forcing the app the quit, there is an app crash report that I send to the developers every time the app crashes. I can take a screenshot and post here the next time the app crashes. It may be worth mentioning that I use Dropbox, and am usually exporting to Dropbox folders. I thought that it might be related to the export dialog opening in folders which are online only, but I just tried it and it worked without error, so I don't think that's the problem after all. Also, here's some version information: MacOS Monterey, V12.4 MacBook Pro (14", 2021) Affinity designer V1.10.5 Thanks for your help, this is a frustrating problem! Especially when I lose changes because I forgot to save recently (p.s. is there a good way to enable auto save with Affinity designer? I see the recovery option in seconds, but I worry that it would affect my system to change that to every 2 or 3 seconds)

This has been happening to me ever since I got a new computer with MacOS Monterey. Affinity designer reliably crashes every time I try to export assets, not sure if the same problem. I have gotten into the routine of saving my work prior to saving, because I can be relatively certain that it will crash at least once before I can successfully export assets. I always send the crash reports, but the problem persists. It seems likely that it's a problem with the latest versions of MacOS. How can I help to debug the issue?

@LibreTraining Thanks so much, that's a great suggestion! I haven't edited a font in the past which is why this didn't occur to me but it seems simple enough. I will give it a shot, or try the file that you've provided. And yes, I meant Hepta Slab, my mistake!

Hi @Sean P, thanks for the quick and thorough reply. And for letting me know about the "Add" bug currently in development. I did ensure that all layers were set to "Winding (Non-zero) before selecting "Add", because that does seem highly related what I saw, but I was still unable to achieve the desired result. While the development team is working on fixing the bug, do you know of any workaround to this problem that won't require me to "Add" each individual character before finally merging the entire string of characters together? Thanks for your help.