- #UNINSTALL FONTEXPLORER X PRO INSTALL#
- #UNINSTALL FONTEXPLORER X PRO UPDATE#
- #UNINSTALL FONTEXPLORER X PRO PRO#
- #UNINSTALL FONTEXPLORER X PRO LICENSE#
I tried using a space glyph " " as a workaround but an error pop-up comes out. I tried to export with no word in it, but as soon as I click export, “Regular” comes back. Now, first thing I did is go back to GlyphsMini, go to “Font Info” and see I have a name box (I suppose) with the name of the font, and “Regular” in another box which, if I delete it, a greyed-out “Style” appears. Used in Illustrator and it looks like the name is still “FontName Regular”
Name: FontName Regular Format: OpenType Style: Regular
#UNINSTALL FONTEXPLORER X PRO PRO#
I imported it in FontExplorer X Pro to do some tests and the file is being read as Only thing I noticed is that the file keeps “Regular” in the name. I just finished my font building, my spacing, my kerning and I’m ready to export.Įverything goes smooth, the font works etc.
#UNINSTALL FONTEXPLORER X PRO LICENSE#
I created an 'uninstall package' combination of deleting the app and prefs plus a couple of scripts.īTW on the server side set the font license reclaim to 30 days (or time limit of your choice) this means that font licenses can be 'reclaimed' and re used if a user does not connect to your server for over 30 days.Using GlyphsMini for a couple of months now and it so much fun! So far when it comes to updates, I have had the best results removing an existing version and then installing the new version package. Their support is good (certainly here in the UK) and they have at times supplied any number of terminal commands to fix the profile specific issues.
#UNINSTALL FONTEXPLORER X PRO UPDATE#
The license/serial is buried in the user profile.įor this reason updates have been an issue, so much so that they released an Applescript 'utility' at one time to run after an update to V2 which caused the app to lock up and demand a new license for each user that logged in.
#UNINSTALL FONTEXPLORER X PRO INSTALL#
I have had various issues with each version of FontEx client when it comes to updates - you will get best results installing during the imaging process or if using Casper remote do it at start up not login, don't Remote install whilst a user is logged in.įontEx is 'profile sensitive' if you install under a 'user login' it will only work for that user and will ask for the license if another user logs on the the Mac.
Ĭhange the any other prefs to suit your working practices.
You should also select the check box to allow 'Admin Free mode', this allows users to run the System and User font cache cleaners under the Tools menu FontExplorer X Pro > Preferences > Advanced> Admin-Free Mode), this is purely self interest as you do not want to spend your time connecting to users Macs to clean up font caches on a regular basis.Ĭhange the default local font store from /Users//FontExplorer X/Font Library to /Users/Shared. (FontExplorer X Pro > Preferences > Font Requests and FontExplorer X Pro > Preferences > Font Requests > Plug-In Manager ).Īllow it to clear the font cache and reboot Composer will capture the clean up and allow you to continue the install/configure as normal.
Now configure user preferences (FontExplorer X Pro > Preferences), don' t forget to select 'Enable interception of font requests' and install the Creative Suite Plug Ins Now add your sever address (Server > Manually Connect) this will be retained when you install for users either during imaging or using Casper Remote. Launch FontEx, and add the license file (FontExplorer X Pro > Client License…). So re image and install all apps, then launch Composer and select 'Normal Snapshot', and install FontEx using 'drag and drop' install. However you should install FontEx Client after any apps you wish to use it with such as the Creative Suite or MS Office. You can capture the install and configuration with Composer as you would with any other app.
0 kommentar(er)
