Topic: crash with testinstalled font • RoboFont

This topic contains 3 replies, has 2 voices, and was last updated by frederik 7 years, 3 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)

Author

Posts
July 12, 2013 at 18:08 #5623

jo
Participant

hello,
test install is a wonderful and very helpful feature.
but I already managed a few times to crash robofont with a font test-installed.
when reopening robofont I get the warning:
“Found some uninstalled test fonts. [Name of the font] It’s required to deinstall these fonts.”
Now I managed to find the font somewhere hidden in private > var > folders … and I can delete the file(s).
But it won’t let me empty the trash and usually requires a system restart. Also testinstalling the same font again wont update the file anymore. Is there any other way to get rid of that file or clearing the cache?
thanks, jo

July 12, 2013 at 19:22 #5624

frederik
Keymaster

RoboFont is popup up this warning when ever it finds a test install which is not deactivated on quit. Those test installed fonts should be deinstalled after the warning.

July 13, 2013 at 12:43 #5626

jo
Participant

thanks for you replay
unfortunately this does not work after a crash. upon reopening i get the warning. i click ok (no other option given) but the font(s) are still there. textedit still has the font in the menu and I can actually use it. only after a system restart it fully deletes the files.

July 14, 2013 at 18:34 #5627

frederik
Keymaster

oh, strange.

Can you look into the console.app and see if there is a notice from RoboFont. It should state: “Succeeded to acivate font!” whenever a font is installed or “Succeeded to deactivate font” whenever a fonts is deinstalled. If something goes wrong it should say: “Failed to activate/deactivate fonts”

thanks
Author

Posts

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.