kaffeeundsalz

That's great, thank you for finding these for me!

Hi folks, does anybody remember the nice keyboard cheat sheets Serif created a while ago for V1? They were even included in the Affinity Workbooks as detacheable cards. This is the forum thread dealing with them: The designs in the thread all use the V1 iconography. Also, I'm not sure whether some key bindings have changed with V2. Did anyone already have the opportunity to update these cheat sheets for V2?

Thank you both. I had hoped for an automatic solution like "don't show when this paragraph style is present on page" or "don't show when this field's name is already used on page" – quite similar to how I can limit paragraphs to e.g. odd or even pages with the "Start" parameter in the Paragraph panel's Flow Options. But I think this is not possible then. I've refined my Master Page logic with what @Brian_J suggested and it works quite well. Thanks again for your help.

Hi everyone, In Affinity Publisher v2, I've created a design for a non-profit organization. The document I'm working on has multiple chapters, each of which occupies a different amount of pages. To make it easier for the reader to see which chapter they're currently reading, I've created a master page with a page header that, among other info, shows the current chapter's name. What I'd like to do now is hide the chapter name in the page header, but only on the first page of each chapter (because that's where the chapter‘s name is written as headline). Is there any way to automatically achieve this? Or would I have to manually apply a modified master page to each chapter's first page? Cheers kaffeeundsalz

I don't think there is a new one. As far as I know, no changes have been made to the inpainting brush tool at all, apart from the new toolbar icon.

It means that instead of a four-leaf clover, you now got a three-leaf clover. If that is what you want to achieve, keep it. The design is fine.

It sounds simple when you say it, but I‘d feel more comfortable if we could agree that it‘s incredibly complicated.

Thinking about it … it probably depends on whether you look at the file or at the application – doesn't it? I mean, even if a software is forward compatible being able to read a file from a newer version, doesn't that mean that the very same file is backwards compatible if it can be read by said older software version? I am tired and my head refuses any logical conclusion. 🤯 😉

What you mean is that there is no forward compatibility. Backwards compatibility would be a newer version of the software being able to read files saved with older versions, and this is perfectly possible in Affinity V2.

No. The video's purpose is to show the difference between clipping and masking, and it conincidentally does this by using shapes. There's not much else you can conclude from the video since it's in no way a complete feature demonstration. That said, on a side note, Serif has never marketed Affinity Photo as a "Photoshop replacement", although many people certainly use it that way. It's entirely possible. You can select multiple adjustment layers in the panel and disable them with one click. Or you can put your adjustment layers into a group and then simply toggle the visibility of the group. You mean so an adjustment layer affects the entire composition? Yes: Put your adjustment layer on the very top of the layer stack and don't nest it. In practice, the two areas where the term is used are mostly unrelated that confusion is unlikely to occur.

I see. Thanks for pointing out the difference.

I don‘t quite understand what you mean. Affinity has the feature to lock the aspect ratio of an object when resizing – in the Transform panel (the tiny chain icon beneath the dimensions fields) as well as when using the drag handles on canvas (sometimes in combination with a modifier key depending on the layer type). Wouldn‘t this kind of proportional scaling always preserve whatever ratio you’ve defined for an object?

To be fair, we don‘t know this. Serif have always said that they‘d provide free updates to version 1 and would charge customers for the version 2 upgrade, but we were never given any time frame when this would happen. Many people expected that version 2 would follow after the 1.9 updates, but as we all know, even that wasn‘t the case. That being said, it‘s entirely up to Serif how often they want to update version 2. The jump to version 3 could happen after 2.5, 2.6 … we simply don‘t know. To be clear, I don‘t really expect Serif to drastically shorten the lifetime of version 2. I‘m just saying that they could. To be clear again, I‘m personally okay with Serif‘s policy, but there are customers who feel betrayed about the current pricing options for whatever reason, and it might be a good idea to point this out to prevent further misunderstandings.

No, it depends on where you position your layer in the layer stack. This is a very basic feature, but since you don't seem to be familiar with it, I'd recommend watching the introductory video about it. For v1: https://youtu.be/CBl20YGZRTk For v2: https://youtu.be/4fiCvurH0is Adjustment layers inside a group only affect the layers in the group. Adjustment layers in the main layer stack affect all layers below it. So I'd expect the effect to be different in either case. If that's not what you mean, please provide an example. Again, that's the terminology that they chose, and in this context, path and curve can be used mostly interchangeably. I don't understand why that poses a problem to you.

That‘s not really a paradox but rather the result of entirely different philosophies from the OS developers. Apple is known for drastically breaking backwards compatibility in newer versions of macOS from time to time. Microsoft is much less radical in this regard. Both approaches have their (dis)advantages. To an extent, this is also possible with Macs using community-developed patchers like OpenCore, getting newer macOS versions to run on hardware that is officially unsupported.