Since Glyphs 3506, I sometimes get this message. Is anyone else experiencing this? Is it a new issue? It has never happened before.
Btw this is the script that has started to cause the error message: freemix-glyphsapp/Insert Glyph to Background.py at master · justanotherfoundry/freemix-glyphsapp · GitHub
Maybe related: In version 3506, Glyphs returns True for isBraceLayer even if it isn’t.
It related to my request where Undo/Redo doesn’t remember the name specified for Undo Grouping (fixed in 3506).
Yes, I’m also getting these messages randomly when running a script, also in the two versions before.
FWIW, in my case, using if layer.isBraceLayer and layer.isSpecialLayer instead of only if layer.isBraceLayer is a quick fix for the undo error message, it seems. I haven’t tested whether this really does what it should, though.
Could you send me the full script and the file so that I can try to replicate this?
This is the script that has started to cause the error message: freemix-glyphsapp/Insert Glyph to Background.py at master · justanotherfoundry/freemix-glyphsapp · GitHub
It occurs whenever there are backup layers in the glyph.
I can’t reproduce it. Could you please send me a file and instructions?
1 Like
In case Tim didn’t send a file, here’s a dummy where I can reproduce it: Dropbox
The /H doesn’t have a backup layer and the script (insert /T in background) works fine. The /T has a backup layer and inserting /H in the background gives this error.
I published a fix today: seems like we need brackets now · justanotherfoundry/freemix-glyphsapp@e288036 · GitHub
Looks like we now need the brackets, i.e. call isBraceLayer() as a method. Has the API silently changed?
The API didn’t change. Not sure why this is a problem now and wasn’t before.