Reminds me of - Bug #906952 “Low performance while manipulating spirograph paths” <https://bugs.launchpad.net/inkscape/+bug/906952>
(performance improves in current trunk if removing the stroke from the large number of copies of the complex path, and assigning a fill only)
Reminds me of /bugs.launchpad .net/inkscape/ +bug/906952>
- Bug #906952 “Low performance while manipulating spirograph paths”
<https:/
(performance improves in current trunk if removing the stroke from the large number of copies of the complex path, and assigning a fill only)