Occasionally when I open a .ufo file, my RF expires, saying that my trial period is over. When that happens, opening any .ufo in Finder gives the same message. But hurray – I can still open RF alone if I don't open a .ufo at the same time. Expiration message is also gone then (until it comes back in 30 days (?). This is of course a bit uncomfortable, since I'm a happy owner of an official license. Version 1.3 on board.
It will return False also if there is a key in the glyph.lib. Main reason is that the glyph.lib contains user set data and when a user has added some data in the lib, like a mark color, but also layers, the glyph has some data so its not empty...
There was a nasty bug in glyph math
The result of some glyph math was always applied on the glyph data, which is not correct. It should return the result as a glyph object, so you can handle the result as expected: set it back in the source or store and used it somewhere else without the modifying the source data.
I will add -= += *= operation do the todo list
maybe I wasn’t clear, I didn’t change the content of RoboFont.app in 10.6 or 10.8, but I just made a link to the robofont-internal python 2.7 on 10.6:
ln -s RoboFont.app/Contents/Frameworks/Python.framework/Versions/2.7 /System/Library/Frameworks/Python.framework/Versions/
Maybe that wasn't even necessary.
There is no output in the scripting window when the crash occurs. In the console, there's this message:
01.03.13 10:24:29,828 com.apple.launchd.peruser.502: ([0x0-0x6d76d7].com.typemytype.robofont) Job appears to have crashed: Segmentation fault: 11
And I've attached the crash log.
Hello, I made my own custom lists of glyphContructions like the one already in robofab (http://code.robofab.com/browser/trunk/Lib/robofab/tools/glyphConstruction.py). For example I have uni021B: t commaaccent.bottom in the list when I run the code everything goes fine, my glyph will be compiled, except the glyph seems to be unchaged… No changed border, no changed header.
Until: I add the glyphname in fontTools.agl 021B;uni021B;TCOMMA
Then everything goes like expected.
Is it really necessary to doe also the agl-thing?