Oh nice! This will be super handy.

@naorem not all extensions have been updated for RF3 yet. we’ve updated some (see activity of the RoboDocs account), and provided upgrade instructions and detailed documentation for developers. but there are almost 100 extensions on Mechanic alone… in the end, each extension developer is responsible for his/her tool.

RoboFab does not exists anymore. see the robofab README and is been replaced by fontParts. I see you already made an issue, great!!

Oops; nevermind! Just found out that macOS has a built-in feature to do this exact thing. Just use the shortcut option + command + w.

@frederik I have mailed you a sample UFO file with the feature issue. Hope you have received it.

@gferreira ok thank you, I have the old metrics machine.

@typemytype ahh, good to know. thanks!

@frederik thanks a ton, it worked!

euhm, never tried that... but will write it down

oh, typo, Ive edited it out, thanks!

there is a known issue in single mode window. This has already been solved in the beta, and is waiting to be shipped in the next release!

Thanks, @gferreira! That was a super helpful suggestion, including the link to the defcon docs. I find that for me, the cannedDesign sort type is seemingly identical to the "Smart Sort" option in Robofont, aside from deleting template glyphs. Still, those are easy enough to re-add manually, and something I don't need to do every time (Add Glyphs -> Import from my "Latin 1" character set... -> then select to "add as template glyphs"). So, the script I'll use is very close to your suggestion, but I prefer this sort type: font = CurrentFont() newGlyphOrder = font.naked().unicodeData.sortGlyphNames(font.glyphOrder, sortDescriptors=[dict(type="cannedDesign", ascending=True, allowPseudoUnicode=True)]) font.glyphOrder = newGlyphOrder

Awesome, thanks for the added clarifications and advice, @gferreira and @frederik!

FYI: in the upcoming release RF3.1 both the magnetic as the show measurements attributes of a guideline will be part of the preferences: defaultGuidelineShowMeasurment defaultGuidelineMagnetic to change the default use, or the preference json editor (alt click the Preferences menu item): from mojo.ui import setDefault setDefault("defaultGuidelineMagnetic", 0)

Hi all, I ran into similar problems recently. Is there any follow up on this problem? Best, N

see mojo.events.publishEvent publishEvent will post to the active tool and all observers. postEvent will just post the notification to all observers and not to the active tool. The difference is the order, the active tool get all the notifications first, before any observer. Depending on the goal you mostly only need postEvent for you custom events. (use reversed domain name for the notification name)

@gferreira said in Stacked Diacritical Mark Construction and Syntax Help: abrevedotbelow = a + breve@top + dotbelow@a:bottom Great! Thank you!

I'm currently having this same issue, as well. I'm in Robofont Version 3.0 (built 1803062007), and I've just re-downloaded Batch from GitHub to make sure I'm not using an outdated version. Here's my error output: Traceback (most recent call last): File "/Applications/RoboFont3.app/Contents/Resources/lib/python3.6/fontTools/ttLib/ttFont.py", line 363, in __getitem__ KeyError: 'name' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/Users/stephennixon/Library/Application Support/RoboFont/plugins/Batch.roboFontExt/lib/variableFontGenerator/__init__.py", line 580, in _generateVariationFont File "/Applications/RoboFont3.app/Contents/Resources/lib/python3.6/fontTools/varLib/__init__.py", line 733, in build File "/Applications/RoboFont3.app/Contents/Resources/lib/python3.6/fontTools/varLib/__init__.py", line 68, in _add_fvar File "/Applications/RoboFont3.app/Contents/Resources/lib/python3.6/fontTools/ttLib/ttFont.py", line 400, in __getitem__ KeyError: "'name' table not found" ​ I might just be doing something silly, but I don't think I'm doing anything too weird. Here are screenshots of my basic font info, the OpenType name tables, and the Postscript Identification fields. I've mostly left things as their default.

this is a known issue and already being fixed in one of the embedded packages: see https://github.com/typesupply/defcon/commit/bce898c1c2e6b24c4774fe9ca6f7a9f5b80ed6a0 this only happens with open contours... a update is scheduled soon

the problem was indeed in the oneToThree extension (now renamed to 1To3). please uninstall the extension, and install the latest version. things should work fine again.