@FosterType Hey Dave. I haven’t tried that. Nice tip, I’ll give it a go. Cheers.

hello @RafaŁ-Buchner, yes, I think it’s a good idea to remove the observer in your code. here’s what the defcon documentation says: Don’t Forget removeObserver The only real gotcha in this is that you must remove the observer from the observed object when the observation is no longer needed. If you don’t do this and the observed object is changed, it will try to post a notification to the object you have discarded. That could lead to trouble. and here’s an example script in which the defcon Glyph.Changed observer is removed when the current glyph changes.

Anthrotype helped me find the issue on on the FontTools repo: https://github.com/fonttools/fonttools/issues/1688 from fontTools.ufoLib.glifLib import GlifLibError from defcon import Font ufo = Font("YourFont.ufo") for layer in ufo.layers: for glyphName in layer.keys(): try: layer[glyphName] except GlifLibError: print(layer.name, glyphName)

hi @erik, there’s CheckParallelTool, but it checks only if the lines connecting on-curve and off-curve points in curve segments are parallel. (checking parallel segments is mentioned in the to-do list)

@connor I think i recall @benkiel had some relevant mastering experience with Vēlo... Any tips, Ben?

Why do you need those tool objects? Im trying to understand your question ;)

I didn't think of that! Thank you, Frederik. This is very interesting.

Hi, this is a rather odd request! It's possible to get menu shortcuts using the getMenuShortCuts in mojo.UI, I was wondering if I can also access its command? I want to introduce shortcuts through a tool that conflicts with RF default keys like "⌘s" or "⌘⇧s" and I want to replace them to "␣s" or "␣⇧s" when the tool is active. But now I want to fire the command that saves the active UFO when the user hits "␣s", it's possible through font.save() but I'm not sure if it works for "Save as" or other menu items. So I want to access the command itself so I don't have to redefine it. Thanks!

Amazing, thanks!

@martin is anything printed to the Output Window during font generation? in my experience, turning warnings ON can slow things down quite a bit. you can turn them OFF in the Preferences Editor: "warningsLevel": "ignore" are you also removing overlaps and autohinting?

Yeah, usually after logging in, I click the logo and then cmd+r to refresh the page. Then search works... same issue with the DrawBot forums as well.

No, nothing of that sort. It was a simple stupid programming mistake that must have existed there since day one, which sounds unlikely, too. So basically I can't explain it. Funnily, the Glyphs version of the plugin didn't didn't have it, eventhough I thought I had kept the core module identical. So it gets even more embarassing :(

hello @RafaŁ-Buchner, this is a great summary and a very valuable test case. please let us know how it goes! something I wish I knew when I was upgrading to RF3: you can use different folders for your RF3 and RF1 extensions. this allows you to start fresh in RF3 without messing up your current RF1 extensions setup. (the extensions folder can be configured in Preferences > Extensions) another place to keep an eye for error messages and tracebacks is the log file. (use the keyboard shortcut ⌃ ⌘ ⌥ O to jump to it in Finder) setting warningsLevel to always is good for detecting problems, but I would recommend setting it to ignore while working. (printing a lot of deprecation warnings to the Output Window might slow things down a bit) ps. most extensions have been upgraded to RF3 by now, so switching to RF3 today is smoother than it was 1 year ago. (those who tried and gave up are encouraged to try again :)

Hello there, experiencing the same issue. RF Version 3.3b (build 1906031450) / ScaleFast 1.0.3 / Mac OS 10.14.6

Awesome, thanks guys!

will be fixed in the upcoming beta and release! thanks for reporting

@gferreira ah I understand. Thanks for the heads up, will give that a shot!

see Open .glyphConstruction files directly in RoboFont

@frederik Haha. I will think about writing it. It also has to add colors if there are not enough colors in the preferences.

@ThunderNixon glad I'm not alone in this! And yes, thank you so much @gferreira for the quick fix! Working now!