I’m trying to eliminate a bunch of calls to resized() which recalculates a bunch of Path() objects. Each path object has about 150-200 elements in it. I briefly broached the subject in this thread: Path Class memory usage
Perhaps I don’t need to worry about the memory usage for these paths and the cost of recalculating them. MakeMusic’s Finale resizes their score windows this way (with the transparent window) so they don’t redraw the score until the new window size is set via the user’s MouseUp. They’re drawing a ton of font glyphs everywhere, so I can see why they wait to redraw until the user finishes changing the window size. But who knows, it might just be a relic of something they implemented in early versions from 2001 or earlier.
Thoughts on how large a path object has to become before redrawing it in a resized() causes ugly slowdowns?