drawinglayer/qa/unit/vclpixelprocessor2d.cxx | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-)
New commits: commit a627a5c694641031694f6472238cc887618bed43 Author: Ilmari Lauhakangas <[email protected]> AuthorDate: Mon Dec 1 12:38:22 2025 +0200 Commit: Ilmari Lauhakangas <[email protected]> CommitDate: Tue Dec 2 20:02:54 2025 +0100 drawinglayer: clarify test comment Change-Id: Ie7a3accf6e9ab769e2f1a420da19efcd4825ca0e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/194873 Tested-by: Jenkins Reviewed-by: Ilmari Lauhakangas <[email protected]> diff --git a/drawinglayer/qa/unit/vclpixelprocessor2d.cxx b/drawinglayer/qa/unit/vclpixelprocessor2d.cxx index 6ad5e6d3e611..7798a1fac4e8 100644 --- a/drawinglayer/qa/unit/vclpixelprocessor2d.cxx +++ b/drawinglayer/qa/unit/vclpixelprocessor2d.cxx @@ -60,11 +60,10 @@ public: processor2d::createProcessor2DFromOutputDevice(*device, view)); CPPUNIT_ASSERT(processor); - // I stumbled over this when hunting another problem, but I have to correct - // this: This test does test something that is not supported. It seems to be - // based on the *misunderstanding* that in the version of the constructor of - // FillGradientPrimitive2D (and similar others) with two ranges the 2nd - // B2DRange parameter 'OutputRange' is a 'clipping' parameter. This is *not* + // A bit of history: this test did not originally test supported functionality. It + // was apparently based on the *misunderstanding* that in the version of the + // constructor of FillGradientPrimitive2D (and similar others) with two ranges the + // 2nd B2DRange parameter 'OutputRange' is a 'clipping' parameter. This is *not* // the case --- it is in fact the *contrary*, it is there to *extend* the // usual definition/paintRange of a gradient: // It was originally needed to correctly display TextFrames (TF) in Writer: If you
