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

Shoot, so... actually, those backslashes single quotes get re-added each time I save, close, and reopen the JSON preferences. So, basically, each time I edit JSON prefs and save, I get this same error, and have to re-fix it. I guess I’ll change the single quote strings to use the glyph name /quotesingle instead of the Unicode.

He Stephen, this is a know issue, Antonio Cavedoni is looking into this, he wrote part of the async url reader.

Oh ok! Thank you very much!

I would fix that first... do you know how you ended up with circular components? This should not be possible in RF, fontParts and defcon...

a workaround is already made (will be present in the next RF beta and the upcoming RF4.1) the core of the issue is an FDK bug see https://github.com/adobe-type-tools/afdko/issues/1168

what font1.defaultLayer[glyph.name] = glyph does: check if the glyph already exists: if it exist it will be removed from that layer: so that the reason why the glyph is at the end of the glyph order in the font overview. (as that glyph is also removed from the glyph order) create a new glyph draw the given glyph in the newly created glyph I cannot reproduce the error, based on your instructions. I will flag this to investigate.

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

@frederik I too have this issue of test installed fonts becoming unavailable after some time. The time they are available varies, sometimes they are gone quickly, other times they hold somewhat longer. Would you have any updates for that issue?

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.

ehum, if the data is incorrect its hard to find a solution for this issue. MM is build as such this doesn't happen :) I dont know what should happen in this case: MM should not create empty kern groups MM should not return empty list for not existing groups as fallback MM should not remove that pair with the missing group. Maybe MM should report, so it gets fixed first. (but there are many edge cases to report...) (Maybe this is a case for ufonormalizer?)

continue here https://github.com/typemytype/GlyphConstruction/issues/52

Noted down and added to the MetricsMachine todo list. The skippeing-glyphs lib key and Metrics Machine originated years apart of each other :)

@frederik I dream of the day someone would convert fontTools feature ast objects to json and we won't use fea file anymore.

looks promising, will check it out

@tallpauley Thanks for the update to run the command! This gives me something to play around with. To take it a step further, is there a lib API I can use to also pull in space center and glyph view shortcuts, like whatever they use to populate their "Hot Keys" tabs? (Btw, I won't filter out commands that don't have shortcut keys, this is part of the allure of having a command palette, you can access commands that don't have shortcuts keys defined yet). I saw mojo.UI.setGlyphViewDisplaySettings, but this isn't all the available commands for glyph view. For space center I didn't see any API in mojo.UI I would dig around myself, but I think you guys compile to .pyc and I don't want to violate the EULA by reverse engineering (hence me actually clicking on the EULA lol). Once I have all the commands available, I think I should have what I need.

Hi @frederik It just never ends, no tracebacks. If I don’t manage to solve it with @gferreira tip I will try to prepare a dummy ufo and post it here. Thank you both!

Okay, that's all for now. Apologies for the long posts! ;)

Thank you. That's great to hear Frederik. Please wait a little with pushing an update. I encountered a bunch of small errors that you might want to have a look at too. Will post them shortly.

hello @ArrowType, the Application Menu page shows only the modifier keys needed to toggle some menu items (such as Preferences Editor, Select All, etc). the keyboard shortcuts for the main menu (for example ⌘+N, ⌘+O, etc) are collected in the Keyboard Shortcuts page. hope this is clear!