Hi Simon, I’m already doing that — it helps a little but less than I thought it would.
Cheers, Jeff. PS: I’m trying out another version which pre-flights the number of strokes, but not the number of points in each stroke. > On 3 Dec 2019, at 15:42, Simon Richter <simon.rich...@hogyros.de> wrote: > > Hi, > > On Tue, Dec 03, 2019 at 03:27:26PM +0000, Jeff Young wrote: > >> Changing the glyph back to a deque (and leaving the strokes vectors) would >> probably alleviate much of the performance hit — but I’m not sure if it >> would bring back the memory issues or not. > > Would it make sense to build it up as a list or deque, perhaps with a > custom allocator, and then copy the contents to a vector once the length is > known? > > Simon > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
