Getting this error now The operation couldn't be completed. There is a problem with an anchor "#entry" in: I
There is just a normal #entry anchor in the I glyph.
I can’t update the features because of this.
Maybe it fixed by rename # to _
No, the # (and more) anchor prefixes have special purposes.
Getting the same error message since latest beta update
I fixed this. Will upload a new version, soon.
Done.
Also not fixed.
This might be the same issue: I use ^entry and ^exit anchors to space the ellipsis.
Glyphs shows me the ^exit anchor but I can’t select it.
This is however only visible the first time I select the component. From the second time the anchor is not shown at all.
You shouldn’t need to select the anchor. And if there is only one option to connect too, the anchor button should not be needed.
There are more anchors inside that are both source and target on top of each other. I can’t change the component to use another set of anchors (in this case the ^entry and ^exit) that is why all the components are placed on to of each other.
The period glyph is used in a lot of places, that is why it contains many anchors.
I want to use the ^entry and ^exit anchors for the ellipsis. They exist but Glyphs won’t let me select them. This is a bug.
Can you send me the file with those anchors?
Done.
I just opened the file again, and now I can use the ^entry/^exit anchors. Glyphs is flakey when I add anchors. It sometimes takes some time before they appear. There is something wrong with Glyphs. I can’t find rhyme or reason: Sometimes they are there, other times they are missing, seemingly by random.
The version 3313 had a bug with anchors. Should be fixed in 3314.
All your versions in the last month or so have had this issue, including 3314. That is the point here: There is something wrong with Glyphs so that anchors sometimes are not available when glyphs are used as components in other glyphs. I sent you several emails about this weeks ago. You seem unable to accept this as fact, but it is. You probably can’t reproduce, and I can isolate the issue, so there we are.
I have a suspicion it has to do with a script, a plugin or perhaps a specific action that changes the undo status wrongly. Script is the most likely. Can you keep track of the scripts you run before it happens?
Hmm, scripts isn’t something I can connect to it. I’ll keep and eye on it, it could be undo related I suppose.
It must be something after which the misbehaving starts. From experience, there’s a typical issue where a script tells the undo manager that all of the steps that follow are to be treated as one single undo. And then something goes wrong and the single undo is never concluded or closed properly. Typical symptoms are that a view doesn’t update properly, like you change the top anchor in e and the composites éèêë still look the same. Restarting the app fixes it.
I had a think, and the only scripts I can connect it to are your Anchor Mover, your Search and Replace in Anchor Names, and then perhaps my MovePointsInAllLayers