@frederik I have emailed you the UFO at frederik@typemytype.com from andy@brandnewtype.com Thanks!

Global guidelines are nested in font objects, and local guidelines are in glyph objects. Aha! That makes so much sense, yet I never thought about it. Thanks @Ryan :) I quickly wrote a script that adds local guidelines with specific coordinates for a list of glyphs. That way I can define the overshoots for /O and /o (that's usually two of the characters I draw in the ideation stage already) and put those values in the code that then adds the guidelines to the list of glyphs I defined and where I need them. It’s not a very "programming" way of doing things, but it gets the job done and it’s pretty straight forward without having to many places I can make mistakes :) I was even thinking about making it a small tool or something inside the inspector where one can store the values for UC & lc and on click remove or add local guidelines. Who knows, maybe I can make Tals tool work for me, then I don't need to do anything by myself :)

(This is something I posted on Slack, but I figured it might be useful to cross-post here for others.) I can’t get my space center “Beam” to show up. This was a problem for me in 4.1 (but earlier as well, maybe) and now is still a problem in 4.2. @ryan helpfully responded with the following code, asking "what’s this output?": from lib.tools.defaults import getDefaultColor from lib.tools.misc import NSColorToRgba from mojo.UI import CurrentSpaceCenter beam_color = NSColorToRgba(getDefaultColor("spaceCenterBeamStrokeColor")) csc = CurrentSpaceCenter() print(beam_color) print(csc.beam()) csc.setBeam(500) Turns out, my beam was a visible color but set super high: (0.0, 0.0108, 0.9982, 1.0) 7856 And the setBeam() method fixed that. Thanks, Ryan! @frederik added to the conversation: makes me think, of an alt menu title for “Beam”: “Reset Beam” which restores the value to the original value (half of the height) ...which is an idea I like! I’m not sure what to tag this, but I guess Feature Request makes sense, as a feature might help others avoid this confusion in the future. After all, I literally went many months without a beam before asking for help, because I figured it was something that was just broken and might be fixed in a future update. 😅 Glad I finally asked, but a "Reset Beam" option could have helped on my most recent serif project!

Should be fixed here https://github.com/robotools/ufo2fdk/commit/99a01d340de3ef3c3d86708c45afebd682daab00 and present in the upcoming beta thanks!

RoboFont is opening a public Slack workspace! It is going to be the perfect space to: discuss the current application development get access to beta updates ask questions and report bugs get in touch with other fabulous RoboFont users The Slack workspace will be open to everyone, you can join it here. Why Slack? A chat, differently from a forum or a mailing list, may allow an easier exchange between RoboFont and the community. Also, Slack is probably already sitting on your machine, as it becomes more and more the tool for professional (or not) written communication for teams. We hope to see you there! Frederik & Roberto

Thank you @frederik @Martin

thanks Martin fixed in https://github.com/typemytype/outlinerRoboFontExtension/commit/8ceebc55a308280e1f4cbc27484a2771eaa3d85e you can update Outliner with Mechanic

the example script shows two different approaches: one is the fontParts setStartSegment on the first contour and an other approach on a second contour You will need to combine and rearrange into a working script. good luck!

The file in your bin folder is a symbolic link to a file inside the app bundle. If you remove the app the symbolic link will not work anymore...

Dear users, RoboFont 4.2 is out! Lots and lots of bug fixes, user interface improvements and a few changes to the APIs. Here's a list with some of most important updates: Layers management moves to a popover accessible from the Glyph Editor and the Font Overview. It is now possible to synchronize mark color, unicode and width across layers In the glyph editor, you can now jump to a component base glyph with alt ⌥ down + triple click The Space Center supports the /?@layerName syntax. It shows the current glyph from a specific layer The Subscriber API gets two new shiny functions: mojo.subscriber.listRegisteredSubscribers lists all the active subscribers with disableSubscriberEvents() context disables all active subscribers while the context is active. This is especially useful to avoid circular events when a subscriber triggers another subscriber, that might trigger another one, and so on. Here an example on how to use it The SmartSet API gets a new editing context with SubscriberEditor(). Check here a few examples on how to manipulate programmatically smart sets Save test installed fonts to a folder inside the application folder According to UFO3 spec, outlines can have an off-curve first point. It may sound silly, but there are reasons for that. Check the updated docs. Keep in mind that the minimum macOS version has been raised to 10.11. Check the release notes: https://robofont.com/version-history/ 
Download available from robofont.com

See the issue to improve the report: https://github.com/typemytype/batchRoboFontExtension/issues/53

Marking this as "solved" for now, let us know if the problem persists!

Marking this as "solved" for now, let us know if the problem persists!

Excellent, thank you for the answers!

Same here 😵‍💫

Thank you!

This works! Thank you Frederik!

@ArrowType Whaoh I came to post this issue too!

Make sure you have the unicodes set, not only the glyph name. Or use uni<hex-4> or u<hex-5> see the GlyphOrderAliasDatabase spec: http://adobe-type-tools.github.io/afdko/MakeOTFUserGuide.html#glyphorderandaliasdb-goadb

Hi, thank you I found the problem :) Now all good