long post :)

1) 2) yep, true that is handy, this is added in 1.3

3) in 1.3 there will be a “Join Contours” in the contextual menu, and double click in the drawing tool to close the contour

4) should it do that? maybe, don’t know

5) renaming is not possible and layers will change a lot when UFO3 gets implemented (not in 1.3)

6) for now, you have to write your own sets of script to handle “group spacing” see http://doc.robofont.com/forums/topic/group-spacing/

7) 8) that is true, its not a text setting tool :)

9) in 1.3 you can

10) there are 4 angles constrains: 0°, 90°, 45° and the proportional angle (=the diagonal from the bounding box, in 1.3 you can eliminate the 45° contain in the prefs

11) shift keyboard zoom with smaller steps makes sense

12) 13) in 1.3 :)

14) can you reproduce that?

15) yep, interesting, will add it

16) soon :)

thanks

mmm, have to look into it
(could also be an FDK issue)

cool, I didn’t knew about this functionality in FL :)

‘shift’ is not the most logic place, will put it under ‘alt’ cause it an alternate behavior

that is a bug, and already solved in the beta, will be in the next release

a workaround:

from robofab.pens.filterPen import ThresholdPen

tempGlyph = RGlyph()
glyph = CurrentGlyph()

pen = ThresholdPen(tempGlyph.getPen(), threshold=10)

glyph.draw(pen)

glyph.clear()

glyph.appendGlyph(tempGlyph)
print "done"

good luck

Just as a general question: are there any extension building guidelines (for design or behavior)?

No there is no actual guide line, but it would be nice if the UI would follow a bit the Human Interface Guidelines

see https://developer.apple.com/library/mac/#documentation/userexperience/Conceptual/AppleHIGuidelines/Intro/Intro.html

Shouldn’t “Copy metrics” be active by default only if the glyph is empty?

Yeah, good catch, this behavior is already adjusted in the beta versions and will be available in the next release.

thanks

This is idd a bug :) and already solved in the beta and will be fixed in the next release.

He Nina

welcome :)

If both the component and the base glyph are transformed, the component will be transformed twice: once with by the moving the component and once cause the component is being moved.

you can ignore it by checking if a glyph as components:

# loop over all the glyphs
    for destGlyph in glyphs:
        # check if the destination glyph is in the font
        if destGlyph not in font:
            continue
        # get the destination glyph
        destGlyph = font[destGlyph]


        if destGlyph.components:
            ## do nothing if the glyph has components
            continue

next issue pops up when there is a mix of contours and components
the best solution is to decompose the glyph or to handle contours separately if you want to keep the components.

## solution #1
glyph = CurrentGlyph()
glyph.decompose()

## solution #2

glyph = CurrentGlyph()

# define a leftMargin, in this cause it should be 10
leftMargin = 20
# the difference between the existing left margin of the glyph
# and the desired left margin is the move value on the x-axis
move = leftMargin - glyph.leftMargin

# loop over all contours and move only the contours
for contour in glyph:
    contour.move((move, 0))

good luck

yeah, python and unicode :)

In the next release RoboFont will check if an unicode value is bigger then 0x10000 (65536) to open a Space Center.