summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuboš Luňák <l.lunak@collabora.com>2015-01-07 17:43:39 +0100
committerMichael Meeks <michael.meeks@collabora.com>2015-01-13 16:02:50 +0000
commit1184218611d1b1b28f0b10879e91388e261b1c24 (patch)
treea2fba517ea3d3e15b80c18f2625b0c3e2081faa1
parent24ed906c3654a844f35a2b2022d9df42618a0a23 (diff)
do not set Y line width to 0
I'm somewhat confused by why there needs to be a separate line width for X and Y, but apparently there is, and the latter shouldn't be just plain 0 (otherwise a number of drawPolyLine() implementations either skip using a simpler path for the usual case of them being equal, or even plain to refuse work at all and cause a fall back). And I hope this doesn't lead to finding out that some of those implementation are actually buggy. Change-Id: I2dbbd1539c4a96d41935cce9ae6565872e2a459b Signed-off-by: Michael Meeks <michael.meeks@collabora.com>
-rw-r--r--vcl/source/outdev/polyline.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/vcl/source/outdev/polyline.cxx b/vcl/source/outdev/polyline.cxx
index ece1d6fe2e6f..78eb139ac6b2 100644
--- a/vcl/source/outdev/polyline.cxx
+++ b/vcl/source/outdev/polyline.cxx
@@ -302,7 +302,7 @@ bool OutputDevice::DrawPolyLineDirect( const basegfx::B2DPolygon& rB2DPolygon,
// transform the line width if used
if( fLineWidth != 0.0 )
{
- aB2DLineWidth = aTransform * ::basegfx::B2DVector( fLineWidth, 0.0 );
+ aB2DLineWidth = aTransform * ::basegfx::B2DVector( fLineWidth, fLineWidth );
}
// transform the polygon