Forum Replies Created
-
Posts
-
He
first make your groups in the Group editor ( http://doc.robofont.com/documentation/workspace/group-editor/ )
if your group name starts with a ‘@’ then you can use it in Kern Center ( http://doc.robofont.com/documentation/workspace/metrics/kern-center/ )Adding a kerning pair hit the plus button at the bottom and the drop down input box should show you all the existing groups that can be used for kerning.
While generating a binary RoboFont ( ufo2fdk ) looks if there is already a “kern” feature present in the feature file. If not it will compile the kerning in side the UFO to a “kern” feature. If you have already declared a “kern” feature it will not be overwritten by the UFO kerning.
hope this makes sense.
good luck
yep that is fixed too :)
He
Form the FL side I don’t know what kind of data
image.dataobject is and how to get the transform matrix. (see http://www.e-font.de/flpydoc/ )But once it is exported you can add the each image easily with
glyph.addImage("path/to/my/image").
If you would know the scale, rotate or the transform matrix you could easily transform the image:glyph.image.scale(x, y) glyph.image.rotate(45) glyph.image.transform([1, 0, 0, 1, 1, 1]) # with a transform matrix
see http://doc.robofont.com/api/robofab-extras/
good luck
mmm, each time you open this window an observer is been added. If you don’t remove the observer when the window closes it will keep getting notifications on current glyph changes and after a while this will idd slow down RoboFont
from defconAppKit.windows.baseWindow import BaseWindowController from mojo.events import addObserver, removeObserver class InterpTool(BaseWindowController): def __init__(self): addObserver(self, "_currentGlyphChanged", "currentGlyphChanged") # do you stuff # ... self.setUpBaseWindowBehavior() self.w.open() def windowCloseCallback(self, sender): # remove the observer to stop getting notifications removeObserver(self, "currentGlyphChanged") super(InterpTool, self).windowCloseCallback(sender)This is already solved in the beta, and will be present in the next release.
naming inside a file isn’t a good idea: all files have be parsed before a menu can be build
will add some functionality to
mojo.UIin the next versionfrom mojo.UI import getScriptingMenuNamingShortKey, setScriptingMenuNamingShortKey data = getScriptingMenuNamingShortKey() data['/path/to/my/python/script.py'] = dict(preferredName="my script name", shortKey="d") setScriptingMenuNamingShortKey(data)
that will being solved in the next version :)
The next version will remember the placement and size of the scripting window.
Did you set a custom template preview font?
Or removed “Lucida Grande” from your system?to solved it execute this:
from lib.tools.defaults import setDefault setDefault("templateGlyphFontName", None)oke thanks for reporting will check if the font is still installed on your system in the next version
good luck
That is a known bug and already fixed in the upcoming release version….
This will change dramatically when UFO3 gets implemented (don’t know when yet…)
RoboFont will follow the spec so components will refer to glyphs from the same layer.
this will be possible in the next version (1.3)
## "point" is a RoboFab point object ## or the index of a point to break the contour contour.breakContour(point)
In the next release there will be some options in the prefs related to the measurements tool: show glyph metrics and font metrics.
Cause there are cases where one doesn’t want to show one of those measurements.
Lots of character sets issues are solved and massively improved in version 1.3:
– writing glyph order / character set back into the UFO in the lib “public.glyphOrder”
– and while opening a UFO it checks if there is a glyph order in the lib
– rearranging by drag and drophope this helps….
can you elaborate what you want to achieve with the special rotation behavior?
you can build a custom tool and draw the selected points your self
s = 5 ## / scale # in a tool you can get the scale value for x, y in CurrentGlyph().selection: oval(x-s, y-s, s*2, s*2)