diff options
author | Luboš Luňák <l.lunak@collabora.com> | 2015-01-07 17:43:39 +0100 |
---|---|---|
committer | Luboš Luňák <l.lunak@collabora.com> | 2015-01-12 13:34:35 +0100 |
commit | a477b66f1fa0847c716c886ab434d8e38247d641 (patch) | |
tree | 609fc9ffc593eb28e51ffef5e7138592b68a8eb0 /vcl | |
parent | ca1f918c327f82568e65f7f49e24b7158c63181f (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
Diffstat (limited to 'vcl')
-rw-r--r-- | vcl/source/outdev/polyline.cxx | 2 |
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 |