lepr

That's an unfortunate artefact of Affinity's technique for rendering its view of the document, and it is not considered a bug by the developers. If you export to PDF and view that in other apps, many, but not all, will present the same artefacts.

You are seeing a deliberate change to the software after the video was recorded, not a bug.

I didn't realise that solution had been provided for Affinity on Windows. That makes Serif's decision for New Layer on Mac even weirder than I thought it was.

But Windows users would not be negatively affected by giving the functionality to Mac users, and there are existing examples of the functionality in Affinity on Mac (as stated in previous posts in this thread) so I find Serif's decision bizarre.

Yes, Quit and Close All Windows for me in Affinity 2.2 on macOS 12.7 with UK English. See addition at bottom of this message. Also, four of the commands in the Geometry submenu change from destructive to non-destructive when the opt/alt key is depressed: Add becomes Add (Compound) Subtract becomes Subtract (Compound) Intersect becomes Intersect (Compound) Xor becomes Xor (Compound) Divide in the Geometry submenu should be affected by opt/alt key, to match the dual functionality (discarding versus keeping open paths of the result) of the toolbar button, but that has been neglected like the New Layer command in the Layer menu. Addition: found an explanation for why some users may see Quit and Keep Windows:

I have Layer > New Layer on my Mac with UK English. opt/alt key has no effect on that. There is also New Layer in the context menu of any item in Layers panel. It is affected by opt/alt in the same way as the button at bottom of Layers panel.

When an object with Gradient Overlay FX is not clip-nested in something, transparency in the gradient affects only the gradient - good. When an object with Gradient Overlay FX is clip-nested in something, transparency in the gradient affects both the gradient and the entire object - bug. An Artboard is a clipping shape, therefore any object with Gradient Overlay FX in an Artboard is susceptible to the bug. Interestingly, the document view exhibits the bug on a Mac but not on a Windows machine. FX result in rasterisation of objects when exporting, but rasterisation proceeds differently when rendering to a vector file format (such as SVG or PDF) versus raster file format (such as PNG or JPG), hence the workaround that has been provided by stokerg. An alternative workaround which will enable correct direct export to raster file formats (and correct document view on a Mac) is to give the susceptible objects an additional Colour Overlay FX whose colour is white and blend mode is Multiply.

Good luck with that. It's yet another permabug from years ago.

You have demonstrated a bug. The problem isn't particular to a Group containing a 'vector-cropped' (actually vector-masked) Image. It affects a Group containing a raster-masked or vector-masked object of any kind. If a masked object has text wrap, the wrap outline is based on the revealed extent of the object - good. If a masked object is in a Group, and the Group has text wrap, the wrap outline is based on the entire extent of the object as if it has no mask - bug.

If R C-R's advice doesn't solve the problem, please attach a document containing an example of a problematic group of objects to reduce ambiguity.

The names of the Saturation and Luminosity blend modes are misleading since they do not correspond to the Hue-Saturation-Luminosity colour model. The Hue, Saturation, Luminosity and Colour blend modes are actually performed in a Hue-Chroma-Luminance colour model. Hue blend mode produces a result with the Hue of the top layer, and Chroma and Luminance of the lower layer. Saturation blend mode produces a result with the Chroma of the top layer, and Hue and Luminance of the lower layer. Luminosity blend mode produces a result with the Luminance of the top layer, and Hue and Chroma of the lower layer. Colour blend mode produces a result with the Hue and Chroma of the top layer, and Luminance of the lower layer.

Assuming you have an open Curve selected: Pen Tool is active: hold down cmd to temporarily activate Node Tool, select the node from which you wish to continue, release cmd key and then place further nodes. Pencil Tool is active: enable Sculpt mode then draw from the desired node.

@thomaso Maybe the following will be of some help to you, although it isn't intended to directly answer your specific questions regarding alpha and compositing bugs. It is an abstraction of an object as a stack of layers. It intentionally omits complications introduced by multiple fills and multiple strokes that are available in Appearance panel. effect is a Layer Effect transparency is the alpha modulation by Transparency Tool mask is any mask-nested entity child is any clip-nested entity there is only one fill there is only one stroke, and it is either 'in front' or 'behind' { effectn ⋮ effect2 effect1 transparency maskn ⋮ mask2 mask1 stroke that is 'in front' { childn ⋮ child2 child1 fill } stroke that is 'behind' }

No, clipping doesn't hinder the filter algorithm. As I said before, clipping restricts the visibility of the filter's result.

One of countless ancient bugs from v1 days: an object/Group with enabled mask-nested Mask, Adjustment or Live Filter is invisible to 'crossing selection'.

You see that the result of a blur extends outside of the border of the source object. Clipping restricts the visibility of the child to the interior of the parent, therefore the result of the blur (the child) is rendered only inside the border of the clipping parent.

The particular problem with that example document exists in v1 also. When a clipping Curve with no fill is not closed, we cannot select its nested content in the document view. If you either close the Curve or give it a fill, then its nested content can be selected in the document view. In my opinion, the problem should be considered a bug.

I believe you meant pernickety/persnickety

Thanks. I see the extra spacing now that I try that. The text has always seemed unnecessary to me, so it's never enabled.

WTF! FWIW, the menu item is Hide Effects on my Mac using UK English.

No wasteful space is inserted when I put all 6 view buttons in the Toolbar on macOS. In fact, the sliver of space that should be between the fifth and sixth buttons is missing.

I guess the video isn't playing correctly for you. There's a document for the first five seconds, then no document for 14 seconds which demonstrates the problem, and then a new document for 5 seconds.

There is something relevant I could add regarding the mathematics of what is happening, but I haven't yet decided whether it would be worth the effort to write it up since the developers' roadmap isn't going to be influenced by it.

I gave you the blending order explanation for a particular scenario we discussed. There was no partial transparency involved in that scenario, and my explanation was correct for that scenario. Your new example which does involve partial transparency is a different matter, and I even remarked that masked groups was something to be discussed at some other time.