lepr

If you convert just one item to an Image object and then create duplicates of that Image object, you'll have multiple references to the one Image, which can be changed to some other image file that is in your file system. Alternatively, try the Symbols functionality. You'll find info in the Help, but come back to this thread if you still need assistance after reading that.

1 unit = width of stroke

Welcome to the Affinity forums Most likely, you will find great improvement by disabling 'Snap to gaps and sizes'.

No, Preserve Alpha prevents the "aura" effect. It should, logically, do that and it actually has worked correctly every time I have enabled it over the years.

Yes, that's what I told you. I disagree. Yes, I said the blurring with Preserve Alpha enabled must happen after the masking. Cool

That and the order of operations is crucial. See my most recent example with four variations. In all four, Preserve Alpha is enabled and blurring is happening after masking.

The bake distortions are a big problem, but a perspective Warp Group itself produces terrible results - circles should become ellipses but they become ovoids, and straight lines should remain straight but many become curved. Example below:

We've all been overcomplicating the solutions. Here's an AP1 document with four simple alternatives which give the same result: blurred background four variants (AP1).afphoto

I'm quite good at that LOL

You can see in the AD document I provided that I didn't have that problem.

They should hire an assistant to click on Edit > Inpaint.

excellent

Wrong. It's there in 'vector view' as well as the 'pixel views'. Your personal failure/inability to see it doesn't mean it's not there. Two videos of the effect happening were posted by v_kyr. Your own video shows the effect! Your own screenshots show the effect!! Maybe a leprechaun is manipulating screenshots and videos to upset you.

blurred background (AP1).afphoto

Exactly the same 'profound effect' is happening in so-called vector view mode, as is proved by your very own screenshots! I feel like shouting, "Are you blind, man?!"

Your Affinity document is using a Pantone process colour, not a Pantone spot colour. Some of the Pantone palettes contain spot colours, while others contain process colours.

The workaround for the last decade (and maybe the next) is to ensure the destination document has same DPI (actually PPI, but never mind) as the source and its unit of measure is Pixel at the moment of pasting.

I have to disagree with the never. Far less noticeable than on a 'standard DPI' display, but still detectable at arm's length viewing distance (depending on acuity of vision, of course).

Your pair of screenshots do show a difference in antialiasing created by changing the Coverage Map. The one with the upward slope in the CM graph has Affinity's standard antialiasing. The one with the horizontal line in the CM graph has no antialiasing and looks jagged. Without intending offence, I'll remind you that you previously admitted to problems with your vision. BTW, please post PNG, not JPEG, screenshots in future. JPEG adds artefacts.

One word: bullsh!t wrong.

In all seriousness, you could easily be waiting a decade or more for the small feature.

Coverage Map affects the antialiasing of the rendering of vector objects, specifically. (I think the OP's screenshot shows normal antialiasing, so I don't know why he finds the display to seem distinctly more jagged than it did the day before.)

Some of your white fills are HSL (0, 0, 100) while others are RGB (255, 255, 255), and Affinity alway considers fills defined with different colour models to not match. Your screenshot of Colour panel shows the padlock enabled to the left of HSL. That will cause a conversion from any non-HSL colour definition to HSL to be displayed in the panel. The padlock must be disabled for the true definition of a colour to be shown when an object is subsequently selected.

@Bitarts See the attachment I added to my comment before this one.

There was a communication breakdown. My advice concerned objects inside a Group because you talked about objects inside a group. I didn't realise you were using the word group to refer to a clipping object rather than a Group. Attached is your document with a very simple change - each of the two sets of windows is now a Group - and you can now use the functionality that I explained earlier. grouped windows.afdesign