Hi, I just updated to 3337 and noticed that cap components with nested nodes work differently now. Not sure if this is a bug or a feature.
I use a cap component to handle rounding of ends of strokes in a really big variable project — in order to achieve this, I need to nest nodes in both the sharp and round master of the cap. The rounded master works fine:
The sharp however started to render like this in 3337:
This worked fine before in 3260. For now the solution seems to be to move either the origin anchor or the first node so they don’t overlap, but it’s not ideal, especially if the cap is used on angled path:
On a related note — I previously reported a strange behaviour, where Glyphs decomposes smart components with nested nodes differently in different scenarios. Whenever there is a mask applied to a path with such component, Glyphs optimizes the decomposed cap by removing the nested nodes. But because different nodes are nested in each master, it results in incompatible outlines that can’t be exported to variable TTF. Is there a way to prevent Glyphs from running the optimization part and just keep the nodes intact?
I would really apreciate some help. Thank you!
