Forum Replies Created
-
Posts
-
this is a formatting bug in the info sheet
thanks for spotting it!Tabbing through the points is already possible, alt down loops over a reversed list of points. If a off curve point is selected it will only loop over off curve points.
This is idd not the standard mac behavior. Will change it to shift down for reversing and alt down for the complete list of points instead of only on or off curves points.
this is a v1.1 bug and will be solved in the next version
there are no print statements anymore captured from FDK after it fails some where (like in your example)
– restructuring the glyph view preferences pane is already for a long time on the todo list :)
– this could idd be a feature when the ‘alt’ key is down
You can define a hot key for jumping to the next of previous glyph in the preferences
You can also define which set should be used for the jumping glyph in “Next Glyph:” drop down menu:
– From ‘All Glyphs’ set
– From selected setsee http://doc.robofont.com/documentation/workspace/preferences/glyph-view/
its idd not the best solution have to come up with a better and more clever way to handle this issue….
The font get messed up cause there is a nominal width set in the font info. If you set this back to zero it should go fine.
RoboFont will check the splines and convert them to two off curves splines in the next version.
(in version 1.1 it doesn’t check WOFF files, but it should :)Although WOFF files with PS outlines should work fine.
Bonus answer: no ;)
Cause the ttf will have splines with more then 2 off curves :)
RoboFont is not checking what kind of data is inside a woff file.
This will be added in the next version.RoboFont is converting ttf splines curves to 2 offcurves splines.That has to be done when a woff contains an embedded ttf.
see http://doc.robofont.com/documentation/workflow/opening-fonts/do you have any features written?
(just thinking about places where things can go wrong)(its a bug that there are no print outs in the output window, this will be solved in the next version)
Yes there will only work in RoboFont, but some have some similarities with the special FL robofab methods.
It doesnt matter if you imported it from mojo.roboFont or robofab.world (inside RoboFont) all robofab object will have these additions.
if you add an observer the callback always receive the current glyph and some additional info related to the event you subscribed to:
the info object is a dictionary and the content changes from event to event.
like mouseDown will have:
"clickCount" : amount of clicks in the glyph view,
"event" : the nsEvent object,
"offset : a offset point used by the glyph view,
"view" : the glyph view(this will change in the next version where a callback only receives a single info dict argument. RF will warn you if you are using the old method)
euh, no you can not look into the source code
they are the same
see http://code.robofab.com/browser/trunk/Lib/robofab/world.py#L97the guideline would be:
– use robofab.world if you want to have your script interchangeable with NoneLab, FL and others.
– use no import: all mojo.roboFont functionality are added to the script locals() (works only when you run the script in the scripting window)
– use mojo.roboFont if you use your script as a module only in RoboFontthat is a feature :)
depending on zoom levels some parts aren’t displayed in the glyph view.
maybe the selection should always be displayed….
(will consider this, cause I know it’s weird that you have no visual feedback)