# List Corner Components in Incompatible Glyphs:
for g in [g for g in Font.glyphs if len(g.layers.paths)>0 and not g.mastersCompatible]:
for l in [l for l in g.layers if l.layerId == l.associatedMasterId]:
print ", ".join( [h.name for h in l.hints] ), "---", l.name
yea frankly this is not particularly helpful.
also i have a script that matches the corners across masters
which does seem to fix it,
that is the incompatible indicator disappears after i run the script and move the paths left and right (so it recognizes change)
but if i open export dialog its back to incompatible again.
very very frustrating
even if i delete all corners from all masters exept one and then manually paste them to the others theres no success
Take a peek inside my Propagate Corners script. You should be able to find all the code snippets you need there. Or perhaps the script suffices for your needs? It takes the corner structure of the current layer and recreates it throughout all other layers.
I have been using the script yes. very useful,
actually i wrote something similar a while ago with the help of a friend ,
since some of the django is beyond my current abilities.
regarding your script:
i asume it checks on each layer in whatever asymetric way u may have corners on any layer and distributes them to all other layers that currently do not have them. What if there are multiple corners on one tho? shouldnt it clean that up too…
So since you have such script maybe it makes most sense that you maintain/extend it for this edgecase.
I suspect other people use this script too and have the same issue i experience.
Don’t mean to sound like i am making demands here,
i understand your time is limited too…
another thing i noticed while skipped through the corners pressing tab is that the corners seem to have a arbitrary order, that is not matching the nodes itself. it seems its based on order of creation. i cant say that seems very logical too me.
shouldnt it rather switch clockwise to the next connected to a node on the path?
one more thing.
this whole thing with corners being incompatible,
seems mainly based on the corner meta data, not on the corner paths.
the paths in my example are compatible and therefor should be interpolatable, regardless of not having the matching names.
im not certain in which cases u would want to purposefully use different corners like this.
just pointing out another edgecase