Change-Id: I33b5d11f850bf405ef5fcf2e6f1fe380287304d0

Change-Id: Ib9cb71a730a8e1480c897ecab2bc502d419f3029

Change-Id: I9f0e84b63ee6e338fc273c137eb1d1470b8185dc

Change-Id: I89a17d645870d9a6a896c738979b1e1f59caa08e

Change-Id: Ice855d69c70d4f5fc119ddf1ddebf18ee6add270

Change-Id: Iafa52d3643b9313c20c75cf98f6b1ec231bf9d6d

Change-Id: Ia45f9776e0b27720647c664541a41b5f46eedc37

Convert method name
  getBoleanComparisonPredicate
to
  getBooleanComparisonPredicate

Change-Id: I00c726b1fecd8352dc49f2af98c3ae3c799ef424

Change-Id: Ic583deda8b0be3c89bcd644a1872ebd83276487a

Change-Id: Ie2366b25a1f81a5b25142e8b9a727bcc2f585c14

Change-Id: I6a19453637ea6de8e8c834ad14d7cdf712671e46

Change-Id: I480fe9a66773bbc6775c6d20c9cf0e2f7e21c230
Reviewed-on: https://gerrit.libreoffice.org/8472Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>

Change-Id: I6365924420f636c8db556d0bce02b2131e540f2c

Change-Id: I95ef44f12ad478677e761edb19528829d33363c9

Change-Id: I386944df28c7e7464e596144a5612a205f5cb967
Reviewed-on: https://gerrit.libreoffice.org/8789Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

A new protected abstract function has been introduced only for
complex gradients. As it stands, we currently need to work out if
we should use a PolyPolygon or a Polygon because, as the comments
say:

    // Determine if we output via Polygon or PolyPolygon
    // For all rasteroperations other then Overpaint always use
    // PolyPolygon, as we will get wrong results if we output multiple
    // times on top of each other.
    // Also for printers always use PolyPolygon, as not all printers
    // can print polygons on top of each other.

Interestingly, the next line is either wrong or expressed badly,
because the check uses PolyPolygons when a VirtualDevice is in use:

    // Also virtual devices are excluded, as some drivers are too slow.

Therefore, I've removed that comment as it seems rather misleading.

Change-Id: Ic496284cb2be8e7e2d348eae76aeeec994e1029c
Reviewed-on: https://gerrit.libreoffice.org/8802Reviewed-by: Chris Sherlock <chris.sherlock79@gmail.com>
Tested-by: Chris Sherlock <chris.sherlock79@gmail.com>

Since commit f59e350d it was impossible
to define a numeric field with a precision of less than 2 decimals, even
if all values were integers. It was also impossible to define a field
width larger than needed for any values in that column. Furthermore, the
integer part was shortened if the overall column's values resulted in
more precision than defined, but the overall length did not reach the
predefined length.

This does not change the behavior of the original intention of
f59e350d to give the precision of number
formats precedence over precision defined in the column header, which is
debatable though because conflicts may silently change the field
definition.

Change-Id: I234c4bceaa1a6aadbd259cb8d9b6cb6f16bf91c2

Change-Id: I473efb4c8233eed1a3a00ce9ab8c1fa84583e2a4

Change-Id: I25d86e2765aae353fa5586244f33728cd5b55bbc

Change-Id: Idfb615063ec8822dee468883c844bab7dba7cf4c

Change-Id: I53241eb41a07546fe4af010246d8ca373b0b1945

Change-Id: I2fbdb95637ee77b444e1947405d64cdd2e0338af

Change-Id: Ibd4abdb0073e20239a220440c14e05f31e88c6a3

Change-Id: Iac0799219df9eb07d1de9886153cbf8390cbacb0

Change-Id: Ibd168ee6a5da734bc3b20bbab698953eb13f0e73

Change-Id: I24f8e817e1f615e8cdab6dde7ede3bce1ab226d2

Change-Id: I5e993b6ad54f7d33b1dfb1ff455281975add2981

One would think there would exist some kind of shim library that would
automatically provide such traces, hmm.

Change-Id: I568d02a2ac70078dee0280d1feb3eab7bbd43030

Change-Id: I1f24a281155ade91f0296dbc24550fcd8febf0d0

Change-Id: I4087f8f51dd6e8066818a98797c1e575ecca3442

Useful for debugging. Also, make the tile border drawing
optional. These three debugging features are governed by environment
variales (set in Xcode before running with Alt+Product>Run...)
DRAW_ONLY_TILE, DRAW_TILE_BORDERS and DRAW_TILE_NUMBERS.

Change-Id: I81f952284676eafe5d204c819658e0225aabdb1c

Change-Id: Ic31f99d6185000660750041065937845d4903bb3

Change-Id: I446c1eb18d45ca9d70690a763bffe1cc144369b4

Change-Id: Iad5076e7717703c7eaea90eeb9ca082aa33cccac

Change-Id: If6202788224b59de7bb6db7a17ab2061c1f6f771

Change-Id: I9764d4e122c4dbab2349499f30c17842e432dadc

Change-Id: I400105321f7bed54d56bd7af4dfd14656293b5b9

Change-Id: I121f437019d45f60017337dea091389ceb8334ce
Reviewed-on: https://gerrit.libreoffice.org/8661Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Change-Id: I533ce52828ae08a6ab111bcbeaaa6b44c62a6ab9

LibreOffice will show a textual description of a style in some contexts
eg in the Organizer tab of the dialog for modifying a style.

This change updates the description of border line types to support
recently-added types: FINE_DASHED, DOUBLE_THIN, DASH_DOT, DASH_DOT_DOT

Also this fixes an out-of-bounds array access in
SvxBorderLine::GetValueString

Change-Id: Ia354a05ab1455eb8bcc079c6e51419a0cc6429d6
Reviewed-on: https://gerrit.libreoffice.org/8781Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>