Thank you @gferreira! I was calling showInterface as a property of the font itself which obviously didn't get me very far!

see Franks comments here https://github.com/adobe-type-tools/afdko/issues/1205

I ran into an issue where the new 3.5 beta would crash on open (as above). I tracked it down to having used vanilla through the external_packages folder. Removing it allowed RF to open normally. I expect RF3.5 includes the newest version of vanilla that supersedes the prior version I had in external_packages.

Hello RoboFont World ! A first beta version of RoboFont 3.5 has just been released. Download RoboFont 3.5b Here are some of the updates in this version: Updated internal packages — Several embedded packages have been updated, including fontTools, fontMake, booleanOperations, fontMath and fontPens. cffsubr is now also included as an embedded library. UFO version as tuple — The UFO format has a new versioning scheme with major and minor version numbers. This is now documented in the UFO specification and implemented in fontTools.ufoLib. Adjustments to Glyph View colors — Based on feedback we received from users of Dark Mode, there have been several small changes to the way colors are composed in the Glyph View. Improved interaction with Smart Sets and tabs — Interaction with Smart Sets has been fixed and improved, and native support for document tabs has gotten better. Better auto unicodes — A small but very useful change: the glyph.autoUnicodes() function now also works with uniXXX and uXXXX names. Generate features with FontTools — The Font Info sheet has a new option to generate OpenType features with FontTools. This prevents overflow issues and offers better support for LTR kerning. …and last but not least: Compatility with macOS Big Sur We recommend users not to upgrade to macOS Big Sur yet! macOS Big Sur, released earlier this month, introduced major changes to the way views are drawn to the screen – which prevented RoboFont 3.4 from working properly. This release makes RoboFont compatible with Big Sur, but also makes it slower. The good news is that we have been working since July with Tal Leming on a whole new drawing system using CALayers, which fixes the issues and offers lots of new possibilities. We are very excited about it, and can’t wait to make it available to you. As usual, see the Release Notes for the full list of changes. And a big thanks to all RoboFont users for feedback, bug reports, feature requests, etc.

don't know the context but you can also use the MathGlyphPen from fontMath to convert all line segments to curve segments

Please don’t upgrade to macOS 11 Big Sur yet! The latest version of Apple’s operating system, macOS 11 Big Sur, was finally released to users this month. Together with a completely overhauled look, it introduces major changes to the way views are drawn to the screen. Unfortunately for RoboFont users, this prevents the current version of RoboFont from working properly on macOS 11. The good news is that we have been working together with Tal Leming since July on a whole new drawing system using CALayers, which fixes the issues, offers lots of new possibilities, and is backwards-compatible with older versions of macOS. It will be included in the upcoming beta, to be released as soon as possible. Thanks for the patience, looking forward to next betas! In the mean time a quick fix RoboFont 3.5 is planned. However it is still not advised to upgrade to macOS 11.

Hey @gferreira, Thank you so much for the fast reply, your code works just as expected!

A few other potential issues: Path directions can change, eg flip a component horizontally Rounding can become an issue, especially if going small or thin Subsetting is a potential issue, depending on the method Also worth knowing that any component with a transformation (scale, rotate, flip, skew, etc) is automatically decomposed when the font is generated.

Thank you for the response. I get it, I think. Address two different problems with the processes for addressing those issues, rather than conflate the code of one problem with the "solution" for the other. Cheers. Now to get the kerning part right!

he Martin you need to generate a binary first yourself, see the docs of RoboChrome Generate your font via RoboFont as usual. For the sbix format you need to generate a TTF, it won’t work with OTFs. If you click the Export to font button now, RoboChrome will know where to look for the TTF you just generated, and will save a copy with a _sbix suffix. hope this helps!

hehe, good catch!

Okay, I think that fixes it! I will probably evolve this a bit further, but here is the code now: https://gist.github.com/arrowtype/a3c4445cd6b9a6174f885eccff38e1c9 (Caveat: Not sure whether it would work for UFOZ)

I just remembered that I asked this question - so sorry for the delayed response! ThemeManager is exactly the kind of solution I was looking for. I'll try it out. Thank you so much!

good it disappeared! enjoy

If public.default is the name of a layer, but it is not set as the default layer, the UFO will not save, and pops up with "The document [file-name] could not be saved. The file isn’t in the correct format." Output window: Traceback (most recent call last): File "lib/doodleDocument.pyc", line 186, in writeSafelyToURL_ofType_forSaveOperation_error_ File "lib/fontObjects/doodleFont.pyc", line 224, in save File "/Applications/RoboFont_3-5b2.app/Contents/Resources/lib/python3.7/defcon/objects/font.py", line 823, in save AssertionError Weird edge case, but took me a while to figure out when I ran into it. The UFO was a generated instance, and I had manually returned it to the foreground (default), background layer naming scheme, so it could work with some of my inelegant scripts.

thanks!!!

No idea, I guess it is a bug in Glyphs...

this should work again...

thanks for the link!

hello @bahman, another option is to include the shared libraries in the extension using git subtree – see the notes here. cheers!