https://bugs.kde.org/show_bug.cgi?id=473164
--- Comment #2 from wolthera <griffinval...@gmail.com> --- So basically, when I was testing this, it seemed that the shape-select/default tool knew what the proper outline is, and converting to path seemed to work. So the outline was occasionally wrong. I still get 'flickers' where Krita will also complain about "KoRTree::insert boundingBox isNull setting size to QSizeF(0, 0)", which I initially thought was related, but no matter how late I put 'clearAssociatedOutlines' in the textLayout code, the flickers would happen, so my current theory is that they're caused by the combo of (parsing svg and populating the kotextshape) + (text layout), which means that direct editing of the inline-size property and having that emit shapeChanged() signal might be a good next step, but I guess I'll get to that during phase 1. -- You are receiving this mail because: You are watching all bug changes.