It is planned in the next big update to implement something like this:
A way to link a node or segment to an anchor, plus some instructions to always update the anchor’s position? I think I already read something about a similar concept in the forum, but cannot find.
Plus, I have a question: Is there a syntax to add some text in an anchor name that is ignored by glyphs (like a comment)?
no.
What kind of comment are you speaking about?
you could add a comment to the anchor’s userData, e.g. GSAnchor.userData['comment'] = 'your comment'
Is this the post?
Something like syntax used for GlyphsData.XML
ogonek@maxX;baseline
That’s what I used to make my demo 
This syntax is currently only used to better approximate the initial position. It can’t center on a stem, only at the bounding box.
I know, but I was wondering if it was possible to set a text in anchor name ignored by glyphs.
I will try to make a plugin to do what I want, and will be really helpful if I could use anchor name to specify some rules instead to use anchor.userData
To make the anchor name work in that way would mean to change almost all code that handles anchors. We are trying to move away from using names to store data (e.g. with the layer attributes that where stored in the name before).
I would suggest to make a custom sidebar property view (like the one for context anchors) to allow input of the extra info and draw that alongside the anchor name
I’m interested in hearing users’ thoughts on this.
Currently, I am considering implementing these dynamic links:
I would like to implement something similar to the existing syntax/system for setting default anchor position in GlyphData.xml.
bg wesh
That’s super cool. It would be nice if you could visualise which nodes the anchor is referring to, like arrows in TT hinting. Also, there may be a use case for simple calculation (e.g. +10 from node, or 30% on the left rather than dead centre).
All this is already planned
Cool, I think it would make more sense to let the arrows flow from the anchor to its nodes instead of between the nodes. Because that’s basically the connection you create.
That way it’s also more clear if the anchor is farther away from its nodes (like if you have that vertically-middle-ish anchor in the /l)
Here is a quick demo with four features :
The curvy line feels strange. Seems like it should be some sort of straight line between the nodes with maybe a tick to represent at which point the anchor is aligning to.
centerX
•----|----•
I imagine the syntax would had some basic math functions like
centerX-10
•–|------•
Is there a demo of what the Sync with 1 node would look like?
