Corner Wrong result after transformed

Scripting
1

I want to transform the shape with four rounded _corners, but we will get the wrong result after transformed.
These corners should also be rounded after transformed, but not keep the original rounded shape.
Could you help.

layer =  Glyphs.font.glyphs["space"].layers[0]
layer.applyTransform([1, 0, 0, 0.5 , 0, 0])
print("done")

cornertest.glyphs (8.0 KB)

截屏2022-01-12 22.05.19
截屏2022-01-12 22.05.191920×1241 95.2 KB

2

You transform everything and that applies to the corners, too. To prevent that, you only should transform the shapes.

3

understood. :grinning:

4

Is there a way to check if a corner has been transformed?

5

The corner object as a scale property. If it not (1, 1), it is scaled.

6

In the UI, you can see and edit the horizontal ↔︎ and vertical :arrow_up_down: scaling in the Info box (View → Show Info, ⇧⌘I):

7

Could this be included in the Smart Filter list? Something along the lines of “Has Transformed Corner Component” or maybe a more general “Is Transformed” so it can be applied to any type of component.

8

For that smart filters, this is perhaps a bit too specific. What would be your use case?

A script could filter all glyphs with a transformed corner component on any layer and add a tag to those glyphs (so that you can filter for them with a smart filter) or write the affected glyph names to the Macro console so that you can do something else with this list of glyphs.

9

Having a smart filter option for transformed components can be useful for

  1. those that use transformations on components as part of their workflow to easily access those glyphs and also
  2. for those that use filters as part of a checklist to see if some component has been accidentally transformed…similar to the filters that check for Master Compatability and Metric Keys out of Sync.
10

I think that is indeed too specific as smart filters. And also might be a performance problem as it would take a while to go through each component and corner and check the scaling.

11

Ah okay. In that case, I’ll figure out a script solution based on Florian’s suggestion.