Stokestack

Thanks. I'm still on version 1 because of that specific issue, along with other unfixed bugs and design defects. I like to support new software developers and perpetual licenses, but I can't reward the refusal to fix glaring problems.

If it fixes the blurring of layers on merge-down, I might consider upgrading.

The simplest and most versatile option is a "no-print" checkbox on every layer. While the label example is exactly why I looked this up in the first place, there are plenty of other use cases. For example, maybe you're doing some kind of separations of your drawing for a creative process.

That sure is an assumption. The fact remains that the proper thing to do is resample all material involved in the marge to match the highest-resolution material involved.

That's a direct reference to the sentence, but the answer to your question is "both."

That is obviously incorrect. The bottom layer is the one getting blurred; this has been shown in numerous examples. Not to mention: The proper solution would not be to blur the higher-resolution layer; it would be to resample the lower-resolution layer to match the higher-resolution one and then do the merge. Anyone know if this has been fixed yet? Now we're up to... three years?

Thanks!

I think the video is pretty self-explanatory, but I can't figure out how to get the text going forward but below the path. Any insight appreciated. curveText.mov curveTest.afdesign

I don't remember if I provided my file to Dan way back, so if anyone from Affinity is still interested please let me know and I'll try to dig it up.

The thing is that this operation shouldn't rely on expressions at all. That's a kluge.

Thanks for the reply. I did open it in another reader (called Skim, a free one that I recommend because unlike Apple's, its search works properly) and printed it to a PDF. Then I opened that one in Designer and was able to do whatever I wanted with it. I'm sure the document has some annoying metadata set, which Designer is reacting to. But not being able to print it (when other apps can) is odd. Anyway, no big deal.

I think this screen shot sums it up. We all know TicketMaster is trash, but this seems contradictory:

Thanks for digging that up, Walt. This actually made me laugh. It's even more ridiculous than I remembered.

If I remember correctly, it has been added in some obscure manner. Check the release notes.

This isn't just about Adobe apps. This feature is also present in Corel Draw and undoubtedly other similar applications. Citing your own experience and "not needing" this feature is a bit pointless. The last time I encountered this problem, I was printing labels. You know what ruins an entire sheet of labels? Having the template printed on them in addition to your text. Now there's a simple everyday case that can afflict "pros" and "hobbyists" alike. What about people who print PCB layouts for heat transfer? Or other uses you may not be familiar with? This isn't "I want the kitchen sink in my software." It's a simple feature that has existed in vector-art programs for decades, and has been requested in this one for its entire existence. If this is hard to implement, there are some profound underlying design flaws in the software.