From 9331d2d333feb911e16f20ce899f2de220bee2f1 Mon Sep 17 00:00:00 2001 From: "Armin Le Grand (allotropia)" Date: Wed, 22 Mar 2023 11:44:52 +0100 Subject: MCGR: Corrected error with Case16 wrong gradient shortcut Also simplified using the test cases, these now depend on an ENV VAR called MCGR_TEST. Fallback is no test. For seeing a multi-color gradient use 1, for Case16 use 16. If active, all gradients are replaced with the one active for the test, 2D and 3D. This is temporary but also for pro build to check for speed there. Change-Id: I90f3c7e59d9d0a3e070a849af3f9ea1c9e5462a0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149316 Tested-by: Jenkins Reviewed-by: Armin Le Grand --- include/drawinglayer/attribute/fillgradientattribute.hxx | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'include/drawinglayer') diff --git a/include/drawinglayer/attribute/fillgradientattribute.hxx b/include/drawinglayer/attribute/fillgradientattribute.hxx index 8a2df4d6baaf..eab442644be3 100644 --- a/include/drawinglayer/attribute/fillgradientattribute.hxx +++ b/include/drawinglayer/attribute/fillgradientattribute.hxx @@ -89,6 +89,13 @@ public: // check if it is defined by a single color, then it is no gradient at all bool hasSingleColor() const; + // MCGR: Check if rendering cannot be handled by old vcl stuff + // due to various restrictions, based on local parameters. There + // may be even more reasons on caller's side, e.g. a + // ViewTransformation that uses shear/rotate/mirror (what VCL + // cannot do at all) + bool cannotBeHandledByVCL() const; + // compare operator bool operator==(const FillGradientAttribute& rCandidate) const; -- cgit