Fontlab UI Destroyed

Randy's picture

I've contacted tech support, but am in a crunch so I'll post here to see if someone has seen and fixed this.

Two days ago, my copy of FL5 went berserk. It launches, but all the palettes are missing as well as the main menu at the top. The only main menu item is Fontlab Studio and there is no "open" "save" etc. Only the standard Show Hide Quit that comes with OSX. I access the app from another user on the same machine, and the menu is there, and it appears to work, but saving and generating fonts doesn't work (this is the full version of FL mind you).

I've deleted the app. Downloaded a fresh copy, installed with my serial and still have the same problem.

So I'm thinking something might have happened with python. I didn't do anything strange to start this (eg. didn't install a new macro or something).

At the moment I'm limping along on a laptop from 2001 so any help would be much appreciated!

nina's picture

Ah, I see you said OSX.

Did you really just delete the app, or did you try using some deinstaller app? It sounds like you might need to clear out stuff from your system that your uninstall didn't catch.

Patrick Witmer's picture

I would try deleting some preferences files as well, seems to fix a lot of my problems like that.

p@rick

andyclymer's picture

Try removing your Workspace file, a lot of the settings for menus and palettes seem to be stored in there. I've had some similar trouble in the past and I believe this is what worked.

Your workspace file is here:

Macintosh HD : Users : [your user name] : Library : Application Support : Studio 5 : Workspaces

Hope that helps...
Andy

Randy's picture

Hmm wish I had tried just the workspaces idea before I killed all the app support. Oh well. Things are now fixed. Thanks all for your advice!

.00's picture

I concur on the advice to delete the Workspace file. Deleting it has solved similar problems for me in the past.

Arno Enslin's picture

In this context a tip for users of the Windows version of FontLab, but maybe there is a comparable way on the Mac:

1. Install the app.
2. Install all macros, you need.
3. Reduce the three main directories, that FontLab uses, to the installation directory; put them together! (Correct the paths in the options dialog of FontLab.)
4. Export the registry keys, in which the paths are stored and create a reg file, that removes all the rest, FontLab has stored in your registry.
5. Make a backup of the FontLab installation directory.

If you have trouble next time, you have your backup and your reg file.

Additionally export your favorite options from the options dialog of FontLab. That’s likewise a reg file.

I have two backups: One with and one without macros.

nina's picture

Sorry for the suboptimal advice, Randy. :-\

Randy's picture

Nina, no worries, thank you for your advice which worked! I had backed up my macro and encoding folders before scrubbing so it was an easy fix. Sounds like it would make sense to optimize my workspace and then back that up too for the next berserkery. Thanks Y'all, case closed and back to work!

paragraph's picture

Oops, my smiley was meant to mean that you need not apologise in my view, Nina.

Bert Vanderveen's picture

Randy, in cases where using a different user account solves a problem one has with an app, the culprit can be found in corrupt/damaged preferences.
Another way to test this is dragging the preferencefile (.plist) to the desktop and restarting the app in question.
For my main apps I routinely make backups of the preference files when everything functions well (because setting up these can be quite a hassle) — or, since the introduction of Time Machine, as a shortcut reinstating the oldest plist available. (The first method is better, of course)

. . .
Bert Vanderveen BNO

dezcom's picture

Kinda makes you wish FontLab would get around to fixing these bugs by now ;-<

ChrisL

Syndicate content Syndicate content