hello @bahman, another option is to include the shared libraries in the extension using git subtree – see the notes here. cheers!

The error is self-explanatory. You are trying to subscript an object which you think is a list or dict, but actually is None. This means that you tried to do: None[something] This error means that you attempted to index an object that doesn't have that functionality. You might have noticed that the method sort() that only modify the list have no return value printed – they return the default None. 'NoneType' object is not subscriptable is the one thrown by python when you use the square bracket notation object[key] where an object doesn't define the getitem method . This is a design principle for all mutable data structures in Python.

you can store your tool specific data in the data folder! defcon has an api for reading and writing files, not for folders inside the data folder. font = CurrentFont() defconFont = font.naked() print(defconFont) print(defconFont.data.fileNames) # data must be bytes defconFont.data["com.bahman.superKernTool.as.bytes"] = b"myData" myData = dict() myData["superkern"] = "foo" defconFont.data["com.bahman.superKernTool.as.plist"] = plistlib.dumps(myData) defconFont.save('test.ufo') good luck

good you found it! kerning values has to be set very precise. Did the extension DesignSpaceEditor show this kern error in the report? good luck!

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

hello @JustJoeDesign, thanks for the note. it’s fixed in the roboDocs fork, update coming soon to Mechanic…

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

fixed inside RoboFont: will be implemented in the next release!!!

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.

Thank you for this!

@frederik Frederik, this is all brilliant!! Thanks so much for digging into it. Importing the multiprocessing code is indeed the trick; the demos work now perfectly. And I can't wait to try out the new async stuff in the next releases! Thanks!!

no, that must be a defcon font object or RFont.naked()

Wait, I did run your script to make sure but looking at fontinfo.plist I find that the value is unchanged and still not an integer: <real>1000.0</real> Changing it manually to <integer>1000</integer> does the trick!

looks promising, will check it out

fixed! it redirects now to the correct page thanks!

hello @flo, happy to hear that the import script worked. you can add features to a font using the Features Editor or with a script: feaCode = '''\ # language statements etc. feature liga { sub a b by a_b.liga; sub ... } liga; ''' f = CurrentFont() f.features.text = feaCode good luck!

Thanks @frederik for this advice. You are right, I have tried to re-use old scripts with RF 3 but without success (I am not very good at that)... I will try to start RF in safe mode and keep you in touch if it solves the problem. Best

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

already fixed, get an update with Mechanic!!