Forum Replies Created
-
Posts
-
He Ronnie
here is a download to an older version… sorry for the inconvenience
He Jaco
I cannot reproduce this…
what extensions have you installed?
or start up scripts?Could any of them overwrite default hotkeys?
thanks
He Franz
The glyph view and space center are sending key events, there is not global key event notification
But to catch (key) events (or any other event) I guess it is the easiest to add a event monitor and a matching mask and a handler
hope this works
just tested a new build on 10.10 and this seems to work
The release date is not clear, but it will be out there when 10.10 comes along :)
an info object has a method
asDict()returning a dict with all the key / values of the font infohope this helps
but
del font.kerning[pair]
should work :)
Hi
this is the default behavior
In not sure why….
Hi
This is idd a know issue, I tested it on the developers preview.
It is scheduled to fix this after my holidays :)thanks
hm, weird
ufo2fdk adds those value correctly into the source .otf before sending it to fdk
see https://github.com/typesupply/ufo2fdk/blob/master/Lib/ufo2fdk/outlineOTF.py#L321-L329This should do it to catch keydowns in a glyph view
from mojo.events import addObserver class testKeyDown: def __init__(self): addObserver(self, "keyDown", "keyDown") def keyDown(self, notification): event = notification["event"] print event.keyCode() print event.characters() testKeyDown()good luck!
you can change the depth level with a ‘hidden’ pref:
from lib.tools.defaults import setDefault setDefault("pythonFileFolderLevel", 100)good luck!
oh, oeps, idd typo, it was redirecting to autoHint instead of stemHist… (will be fixed in the next update)
stemHisttakes a binary path as argument.and has optional arguments:
* useCurves=Bool: Include stems formed by curved line segments; by default, includes
only stems formed by straight line segments.
* blueZones=Bool: Return alignment zone report rather than stem reportthis is a Adobe FDK tool.
The mojo module is just a collection of useful internal modules. You can also use this:
from lib.tools.compileTools import stemHist print stemHist("binaryPath.otf", useCurves=True, blueZones=False)good luck
there have been some discussions on the beta list about this:
the next implementation will be:
components in dark gray and hard contours in black. it will be almost not visible when there are only components but when ever there is a mix of contours and components it clear.if you have other ideas you could send me your configuration (use inside DrawBot)
from defcon import Font from fontTools.pens.cocoaPen import CocoaPen # set a path path = u"path/to/my/Font-Regular.ufo" # get the font font = Font(path) # get a glyph both with a contour as with a component glyph = font["tcaron"] # background fill (same color as the window) fill(237/255) # draw rect with the size of the canvas rect(0, 0, width(), height()) translate(100, 100) scale(.8) # fill with black fill(0) # get a pen pen = CocoaPen(font) # draw the glyph in the pen glyph.draw(pen) # draw the pen.path drawPath(pen.path) # new pen componentPen = CocoaPen(font) # draw only the components in that pen for component in glyph.components: component.draw(componentPen) # set a fill # component fill color # 50% black with a 30% alpha value fill(.5, .5) #stroke(1) # draw the compontens path drawPath(componentPen.path)you can always use “contains” or “match” options
but it would be idd a lot nicer when the colors are updated when ever a glyph.mark is added or changed…
There is no difference between just executing a script or an extension. In some cases an extension is easier when the tool or added functionality gets bigger (with embedded modules) and when there are assets (like icons).
Extensions have a info.plist which is handy to share, check versions and fe Mechanic is using that to download the correct packages from github….
Otherwise you can also set start up scripts in the prefs. Those gets executed during start up.
good luck!