Chris Christner

Of course, after I restarted, I thought of the things I should have done instead, such as making a screen capture so I could rebuild the file from scratch. Your suggestions would have worked better too. Unfortunately, I just started using v2 today after umpteen years of working in Photoshop, which as I've mentioned earlier has reliability problems, but even when it crashes, you still have the source file, maybe missing the last work you've done, but the file is still intact. So I was in Photoshop mode when I just restarted thinking that I could reopen the file and make the few changes that were needed. Wrong. Thanks for your ijnformative but depressing post! I was hoping the problem I'm having was rare.

I tried reopening the file just in case it healed it self. No joy. But here's the error message it displays: Syba 8 Bay SATA Enclosure SY-ENC50119.afphoto was created in Affinity 1. Editing it will make it unusable in the older version. Use "Save As" to preserve the original file. The image was created today in Photo v2, not v1. After I click Continue this displays: Failed to open file /Users/username/Documents/Syba 8 Bay SATA Enclosure SY-ENC50119.afphoto The file type is not supported. It boggles my mind that the image was there on screen and could still be edited, but it couldn't be saved.

Thanks for pursuing it! I had to select the Library icon while holding option, not click on the library > application support option at the bottom of the panel. Anyway, there is an autosave folder but nothing is in it. Really appreciate your help!

Thanks for the help! It sounded like good advice, but macOS 15.4 (Sequoia) does things differently so there's no affinity or affinity photo 2 folder listed in the application support folder.

I've been using Photo v2 on my Mac M4 Mini today and had put a lot of work into an image. Having used Photoshop for years and seen it crash right when I was nearly finished, I saved this Photo image often. As I was nearly done with it, I saved one more time and an error message appeared saying Photo couldn't save the file because it had lost lock. Well that's disappointing. So I tried to do a save as to the Desktop and that failed! I was forced to quit and restart the Mac to see whether the file could be salvaged. It cannot. This is crazy, how can Photo be so fragile and show such disregard for my hard work?

Just what I needed. Thanks!

Publisher has a split screen mode, but it's split between pixels and vector. What I want is a split screen that divides the screen horizontally or vertically so I can work on different sections of the doc at the same time. Is there such a capability?

The workaround on a Mac is to select the template files that have custom extensions and do a get info, then click the "Stationary Pad" button. Opening the docs will create a new file with all the content of the template but the template can't be overwritten. Don't know if Windows has a similar setting.

And that works really well! Thanks for the help.

I understand that each Affinity app can save a template file with a .aftemplate extension, and that the templates can be opened in any of the suite applications. But to avoid confusion, why not give each app a unique template extension so it'll open in the correct application? Then if you want to open a Publisher template in Designer, you can simply open it from inside Designer.

It ain't pretty, but it'll work. Thanks again!

I'm betting you'll have a workaround as usual. Appreciate the help!

The problems I have with that are: there's no way to set the B&N tabstop by eye (which is how I like to work) and I don't see why B&N can't just work with the text ruler tabstop. Where's the advantage to it being a specific setting? As a workaround, the tabstop could be set by eye or clicking on it could bring up a field for entering the precise position. Anyway, I thought it was a bug, but it turns out they like it that way. So I'll adapt.

Because both settings control where the text is indented. Hence they should be the same.

As shown in the attached image, I created a bullet style and adjusted the tab stop to where I was satisfied. But the first line of text kept indenting to what I later learned was the tabstop setting in the Bullets and Numbering panel of Paragraph. Am I missing something subtle or is it a bug? Because it seems like the B&N tabstop should be the same as what I set with the ruler tabstop.

Update: Following advice from this topic (Thanks all!), I requested a refund from Apple, and received it today.

As I recall, webp exporting was tentatively scheduled for 1.9. I didn't see it in the beta, so is it going to be in 1.10?

Actually, I haven't contacted the App store because SFurniss gave me the affinityreturns@serif.com address. I emailed it and got an auto-response. Are you saying they're not likely to refund the purchase and that I have to contact the App store?

I didn't know that's how it works. Thanks for the explanation. Part of the problem is that the App store is so flaky. You download software and pay for the pro version. Next time you download it you get the basic version, so you have to click on the buy button, at which point it tells you that you've paid for the pro version and downloads that. That's what threw me, because I expected the store to download the version I'd already bought, not realizing I must have bought it at Serif's store. Anyway, they're giving me a refund, so all's well that ends better.

I'll do that, thanks!

Hmmm. Why would that be a separate purchase? I mean, if I buy it from the Serif Store or the App Store, it's all registered to me, so it shouldn't matter. I hope they'll refund the money.

I already have a license for Publisher, but after doing a clean install of MacOS High Sierra, I was charged for Publisher (not Designer or Photo). Please fix this. Thanks, Chris

I need to get glasses, because when you suggested this earlier, I missed the S in the P and T panel and tried clicking on the S in Typography instead, which didn't work. Now that I've found the S it does exactly what I need.

Thanks, that's the workaround I'm using too. I created a character style with the font, size, and baseline I needed for superscripting. Of course it's only good for that font and size, but it works.

I understand their reasoning, but it's flawed, otherwise the top apps in the industry wouldn't be using faux characters to annoy their users' customers. For purists with lots of time on their hands, I'm sure they admire Affinity's stance on this. Those of us with deadlines to meet...not so much.