Performance for glyphs with many points

RoboFont Forums Enhancements Performance for glyphs with many points

Tagged: 

This topic contains 4 replies, has 2 voices, and was last updated by  frederik 3 years, 9 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #5681

    Robin Mientjes
    Participant

    I’ve been working on a distressed handwriting font and have noticed that point counts over 50 slow down the app into unusability. That is without Space Center open. Point removal often shows the ghost of whatever I just removed. I am reconsidering every part of this project at this point, it is that slow.

    This is on a MacBook Pro Retina 13″, latest public release on Mountain Lion, 10.8.4.

    #5682

    frederik
    Keymaster

    weird, it should not become any noticeable slower (only when you have a massive amount of points, just did a quick test with a 1000 point glyph)

    what kind of extensions do you have installed?
    are there tracebacks in the output window?
    are there logs in the console.app?

    #5683

    Robin Mientjes
    Participant

    Interestingly, when I try to select outlines (Command-Shift + drag) the output window tells me

    Traceback (most recent call last):
    File “lib/eventTools/editingTool.pyc”, line 194, in _mouseDown
    File “lib/eventTools/editingTool.pyc”, line 330, in mouseDownSingleClick
    File “lib/eventTools/editingTool.pyc”, line 231, in mouseDownMagicContourSelection
    File “lib/fontObjects/doodleSelection.pyc”, line 509, in addContour
    File “/Applications/RoboFont.app/Contents/Resources/lib/python2.7/defcon/objects/glyph.py”, line 342, in __getitem__
    IndexError: list index out of range

    #5684

    Robin Mientjes
    Participant

    It seems that the stencilPreview script was causing some other problems, actually. I did not notice this with more common point counts, but it became hugely problematic above 50. There was no stencil layer, and I wasn’t trying to stencil a handwritten font, but it was causing a mess. Removed it and got much better performance.

    #5686

    frederik
    Keymaster

    good you found it!

    “printing” a traceback is very costly, but handy so you know what went wrong

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

You must be logged in to reply to this topic.