https://bugs.documentfoundation.org/show_bug.cgi?id=150551
--- Comment #13 from Armin Le Grand <[email protected]> --- Why not, it's on gerrit now: https://gerrit.libreoffice.org/c/core/+/140354 This puts it at least to the state before the change leaded to this regression. To do more I would need to know more why the two ::processPolyPolygonGradientPrimitive2D methods were added. The one at VclPixelProcessor2D only replaces the case that start/end color are the same, but not even calls older (faster?) vcl methods, so I see no gain there, but may overlook something. BTW that useful check/optimization should go to PolyPolygonGradientPrimitive2D::create2DDecomposition, so all renderers (now and in the future) would use that optimization. In the end the decomposition of the resulting create2DDecomposition creates a single polygon, but it's embedded in a MaskPrimitive2D in PolyPolygonGradientPrimitive2D::create2DDecomposition, so the optimization in VclPixelProcessor2D::processPolyPolygonGradientPrimitive2D is better here, but - as explained - will only have effect in VclPixelProcessor2D since not added to the decompose. The one at VclMetafileProcessor2D should not be time-critical at all since it's for creating metafiles. It leads to regressions, as we see... -- You are receiving this mail because: You are the assignee for the bug.
