Old topic but still, I had the issue too. So here is the solution : MM provide a subtable option for writing kerning into fonts. This disable the overflow issue when generating fonts.

Thank you!

This is and know issue and already solved in the beta!! you can get the beta by joining the slack group, if you want: see https://forum.robofont.com/topic/1031/robofont-community-slack-workspace

in the docs: https://fontparts.robotools.dev/en/stable/objectref/objects/kerning.html#fontParts.base.BaseKerning.find

I resolved my AppKit problem by opening a new terminal window and installing PyObjC with pip install -U pyobjc

oh yeah, sure contour.points it is in a fontParts world thanks!

Thanks Paul!

@frederik Thank you - seems like the issue is now resolved!

oh this is hard :) You are missing image data which is stored in the memory only. f = CurrentFont().asDefcon() g = CurrentGlyph().asDefcon() # a font object has a centralised images object collecting all image data. print(g.image.fileName in f.images) # if the fileName has no data, the image doesnt exist in memory and on disk

@roberto-arista said in RF 4.1 crashing issue with Mac OS Monterey: from mojo.extensions import ExtensionBundle for extension in ExtensionBundle.allExtensions(): bundle = ExtensionBundle(extension) print(bundle.name, bundle.version) Thanks, @roberto-arista here is the result .... Add Overlap 1.2.3 AdjustMetrics 1.0 Copy Glyphs 1.3 CrossOverlap 0.4 Curve Equalizer 2.0.3 FeaturePreview 1.2.5 Glyph Nanny 2.0.2 Glyph Construction 0.11 Italic Bowtie 1.2 Mechanic2 1.8 MetricsMachine 1.1.3 PathOperator 1.1 Prepolator 1.4.5 ScalingEditTool 1.0.4 ShapeTool 1.9 word-o-mat 3.1 .... .... For your information, I did remove & reinstall Mechanic2 with all these extensions.

With UFO the starting point (first point in the contour list of points) is not always a on curve point. As a UFO just makes a loop. The symbol for direction of a contour looks very strange when its attached on a off curve point. So yes after 40 years being one, you'll have two now! This change in the recently in RF4.2. And is important to visualise the data correctly. The conversion between quad/cubic should maintain the startpoint if it was an on curve. (an issue to fix is being made)

I tried both .glif in RF and they work fine. Was it maybe a sync issue with git? Did you have to solve any diff conflict?

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 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