Topic: Bug on deleting contours • RoboFont

This topic contains 5 replies, has 3 voices, and was last updated by traviskochel 8 years, 9 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)

Author

Posts
October 10, 2011 at 15:01 #1032

JBL
Participant

Deleting a contour, and trying to click the remaining outlines yielded this:
Traceback (most recent call last):
File “lib/eventTools/editingTool.pyc”, line 195, in _mouseDown
File “lib/eventTools/editingTool.pyc”, line 301, in mouseDownSingeClick
File “lib/fontObjects/doodleSelection.pyc”, line 373, in addSegment
File “lib/fontObjects/doodleContour.pyc”, line 55, in _get_segments
AssertionError

January 1, 2012 at 02:27 #3452

traviskochel
Participant

I too get this error once in a while. Sometimes restarting RoboFont resolves the issue, but not always. The original outlines were exported from FontLab using the robofab script, if that helps?

January 1, 2012 at 12:09 #3533

frederik
Keymaster

Do you remember you copied the contour in RoboFont first? There was a bug in copy paste (you see the starting point jumping) during copying contours. This should be solved in the next version (1.2)

January 2, 2012 at 19:33 #3577

traviskochel
Participant

It seems to happen even on shapes that haven’t been copied/pasted.

Trying to narrow down the problem, it seems to happen when more than one points are selected. Specifically when one of them is the starting point. I’ve uploaded an example here: http://tktype.com/deletepointbug.png

When the selected points on the left are deleted, the problem arises. On the right, with the outer contour’s starting point moved, I can delete them with no problem.

January 2, 2012 at 23:08 #3578

frederik
Keymaster

thanks for reporting
this should be solved in the next version

January 2, 2012 at 23:45 #3579

traviskochel
Participant

great! thanks
Author

Posts

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.