https://bugs.kde.org/show_bug.cgi?id=413220
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://invent.kde.org/kde/
| |krita/commit/c15d8888c3d793
| |a31c914ffb80a5b38a1f2846ad
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Dmitry Kazakov <dimul...@gmail.com> ---
Git commit c15d8888c3d793a31c914ffb80a5b38a1f2846ad by Dmitry Kazakov.
Committed on 08/05/2020 at 17:18.
Pushed by dkazakov into branch 'master'.
Fix artifacts when rendering complex selection outlines
It happens because of a bug in opengl-based stroking algorithm in Qt.
And it happens only when one tries to draw a path with multiple
subpaths. The easiest workaround for this bug without patching Qt is
to manually split a multi-subpath path into QPainterPath objects with
only one subpath in each.
It might happen that the resulting subpath generated by the QDashStroker
will have no lines at all. It happens when further LineToElement items
compare as equal to the starting MoveToElement when compared in 'float'
space. In such case QTriangulatingStroker::process() skips LineTo elements
and the vertexBuffer ends up with unconnected vertices, which generate
unwanted triangles.
Related: bug 419240
A +80 -0
3rdparty/ext_qt/0100-Fix-artifacts-when-rendering-multisubpath-dashed-QPa.patch
M +5 -0 3rdparty/ext_qt/CMakeLists.txt
https://invent.kde.org/kde/krita/commit/c15d8888c3d793a31c914ffb80a5b38a1f2846ad
--
You are receiving this mail because:
You are watching all bug changes.
