Hi Frederik. In testing 3.2, it seems to be showing the same behavior.

Somehow something wrote a wrong value somewhere in the font.info, I know this is not helpful. This is not possible with the font info sheet as everything is either validated or normalised when setting into the font info. Does the font info sheet open for this font? You can test where it goes wrong or which attribute has the wrong value with this script: from fontTools.ufoLib import fontInfoAttributesVersion3 # get the current font f = CurrentFont() # to test set a wrong value somewhere # f.naked().info.styleName = 1234 # loop over all attributes for attr in fontInfoAttributesVersion3: # ignore the guidelines if attr == "guidelines": continue # get the attribute from font info getattr(f.info, attr) when # f.naked().info.styleName = 1234 is uncommented you should receive this error message: Traceback (most recent call last): File "<untitled>", line 6, in <module> File "info.py", line 38, in setter raise ValueError("Invalid value ({0}) for attribute {1}.".format(repr(value), name)) ValueError: Invalid value (1234) for attribute styleName.

I see. Yes that appears to change the reference point for the transformation, but it still transforms all off-curves. With a script, do you mean creating a custom transform tool? It would be great if there were a preference that is point-type-agnostic transformation as well

In RF3 the kerning icon in a font window is not MM anymore, RF just shows a kerning icon and opens RoboFont default Kern Center. However it can happen MM is listed ‘Edit With’, apps supporting UFO (similar as in Finder).

I see... they will be added

the font.lib is also possible but then its hard to have the global undo manager focus. The current undo manager is connected to the current glyph. good luck!

That is correct @ConnorDav some extensions are not ported yet... follow the issue and progress in the robodocs repo.

Perhaps I’m doing something wrong, but the kerning transformations with reference groups don't seem to be working in the extension. Here's some screenshots of some valid groups and transformation syntax. It works in the MM App (4.0.5).

@frederik Ah, ok. That sorta makes sense. I imagine there is some deep logic to figure out here. In the mean time, could the wording perhaps match the group editor and exception dialog? At the moment it's Side 1 | Side 2 in the group editor, and Kern 1 | Kern 2 in the exception dialog.

TL;DR a long text string in MM preview window slows it to a crawl. Can it be faster? When I kern a pair of letters, I have a string of words in the preview window to check them in context. For example, if I’m kerning an Upper/Upper list and I’m on J/UC, I'll paste this string into the window: J JARN ENAJER HEBJORN HOCJERM HODJERN REJOINER FJERNISCHE LAKJERNIS REJOINER KLIPJENNI MARJORAM SJORNE MATJINKO JUNIPER HUJIME HIVJINE HIJVINE HIJWINE HIWJINE HIJYINE HIYJINE HIZJINE HIJZINE A string this long really slows the extension to a crawl. The old standalone MM app used to handle a string like this. Is there any way to beef up the extension somehow? I’d really appreciate it!

@gferreira Thanks for helping!

mmm I see the problem is that its edits the blue zones, and when the font info has changed, RF will update tons of views and cells... I would store it temporarily in font.lib while editing (as you want to jump to different glyphs and see the same values). When not editing (dragging fe) write it back in the font.info.

mmm, see Character Set Preferences There is a default font and a fallback when there is no unicode. I guess its up to the user to pick a font that contains the glyph.unicode, if a unicode is not in the selected font, the system fallback font is used to draw the template glyph.

Hi everyone, I recently turned off autosave and ran into the same problem. Here's the output window: ******************** Could not save glyph 'n' in layer 'foreground' Traceback (most recent call last): File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/ufoLib/glifLib.py", line 268, in getGLIF FileNotFoundError: [Errno 2] No such file or directory: '/var/folders/ww/8szzh9td0w95r2pm89_516_h0000gn/T/tmpsttvw8ln/temp.ufo/glyphs/n.glif' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "lib/fontObjects/doodleLayer.pyc", line 238, in saveGlyph File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/defcon/objects/layer.py", line 578, in saveGlyph File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/defcon/objects/layer.py", line 592, in _stampGlyphDataState File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/ufoLib/glifLib.py", line 282, in getGLIFModificationTime File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/ufoLib/glifLib.py", line 272, in getGLIF KeyError: 'n' Could not save glyph 'u' in layer 'foreground' Traceback (most recent call last): File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/ufoLib/glifLib.py", line 268, in getGLIF FileNotFoundError: [Errno 2] No such file or directory: '/var/folders/ww/8szzh9td0w95r2pm89_516_h0000gn/T/tmpsttvw8ln/temp.ufo/glyphs/u.glif' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "lib/fontObjects/doodleLayer.pyc", line 238, in saveGlyph File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/defcon/objects/layer.py", line 578, in saveGlyph File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/defcon/objects/layer.py", line 592, in _stampGlyphDataState File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/ufoLib/glifLib.py", line 282, in getGLIFModificationTime File "/Applications/RoboFont.app/Contents/Resources/lib/python3.6/ufoLib/glifLib.py", line 272, in getGLIF KeyError: 'u' Before opening this file I turned off autosave after reading @FosterType 's reply. Here are the steps I made in creating this error: Opened the file, it was a UFO 2 and was converted to UFO 3 Moved a few points and handles. I did NOT create new points, segments, or contours. I did NOT make any new glyphs. The 'u' is a component of the 'n' which I assume is why it is producing the error on both glyphs. I noticed that in the RoboFont preferences my Autosave path was configured like this: user/Library/Autosave Information A classmate of mine who has not reported any issues like this had his AutoSave path configured in this way (he didn't remember doing this himself or if it carried through from an old Robofont install). user/Library/Application Support/Robofont/Autosave It's worth noting, this problem occurred AFTER I turned off Autosave, BUT I had not shut down and restarted Robofont yet. I did the following and the error did NOT reproduce: selected all points and segments and contours deleted the glyph from Font menu pasted the glyph data back in place I shut down RoboFont and restarted it. Opened the file again and moved through the existing glyphs moving the points and saving and I have not been able to reproduce the error. This could be because the Autosave preference has been updated. Hope all this helps!

@frederik Thanks. I'll give it a try.

Those could be added, I guess. Where features are generated for a given set of ufo files.

@frederik huehue, ok, so we have to live with that

@benedikt said in Traceback when sorting AllFonts(): fontParts.world.FontList these functionalities should be provided by an implementation and not by fontParts, similar to CurrentFont, CurrentGlyph, CurrentLayer, CurrentContour, CurrentPoint,... FontList is optional but could be provided by an implementation.

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

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