Hi @gferreira, That is good to know! Thanks for sharing.

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 :(

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

legends, thanks for the help!!

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 and @gferreira Thank you so much for both of your insights. I'm relatively new to UFOs and Python, and appreciate any corrections. I chalk them up as guidance on my journey to becoming educated through my missteps.

Hi @gferreira , Thank you so much! Totally fixed the problem :) Cheers, Elle

A fresh public beta is available for download: RoboFont 3.2b. This looks like it will be the Golden Master or Release Candidate for RoboFont 3.2. Main changes in this version: Support for single file .ufoz: a compressed UFO3. This will be slower in reading and writing but works better with services like dropBox. several bug fixes both in external packages as internally. Update of internal packages Special thanks to all beta testers & users for their precious feedback and feature requests. Enjoy!

(the question was answered here)

RoboFont 3 has landed. Finally! From the outside, very little has changed… but inside: UFO 3 Python 3 With RF3 comes also a new website, a new documentation, and a new forum. Read more about the changes in RF3 here. See the version history for the full list of changes and additions. RoboFont 3 requires a new license... If you bought RoboFont 1.X after 08/Mar/2017, you will get a full discount. Contact the team with your order number for details. As always, many thanks to all the beta testers & all users posting on the forums for their precious feedback and feature requests. enjoy! The official RF 3.0 release was held back by a few months because of an issue which affected updating extensions using Mechanic. This issue was solved with Mechanic 2 – read more about it in the Robofont 3.1 release notes. original announcement date: 06 March 2018

there is a known issue with RF3 and temporary licenses. An update is scheduled soon. I hope this helps

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

PenBallWizzard is finally available for RF3 since a few weeks ago. thanks @frederik for doing the hard part! if you have already installed with Mechanic2, please uninstall and install it again. it will not show an ‘update available’ message because the extension repository changed.

great news, it would be nice to give the beta version a test, so yes please, thanks a lot!

@frederik Oh that makes sense. Neat—I'll get used to that.

done

hello Erik, drawBot becomes available as a module when you install the DrawBot extension.

This will be fixed in the next update. Planned somewhere around the end of the week or early next week thanks!

all issues related to extensions in RF3 were solved with RF3.1 & Mechanic 2. if you still have any problem, please start a new thread. thanks!