and PolyPolygon::Optimize in tools to useful fallbacks when working on
PolyPolygons (what they do *not* support)
(cherry picked from commit dbe489ab9766d96c5cafb079bc4778103bded783)
Conflicts:
vcl/source/gdi/outdev4.cxx
Change-Id: I5d2374ec95702cb0cab29d2e82710d4aa29fa823
using a all-points count and a all-points array
(cherry picked from commit 8ee49906f04106317997e9ca3bb890870816e274)
Conflicts:
svtools/source/filter/wmf/enhwmf.cxx
svtools/source/filter/wmf/winwmf.cxx
tools/inc/tools/poly.hxx
tools/source/generic/poly2.cxx
Change-Id: I57f7f08d8dd87c83c30ab2d16ca22b772b2bd834
The time when it made sense to use "clever" #ifdefs to, for performance or
compiler reasons, conditionally bypass private parts of a class declaration
passed a decade or longer ago.
Still more of this in sw and sc. People working on those modules might want to
do it too, or not.
Change-Id: I1053139ca5e5e2631f7b22d99d3bada54fc337be
Reviewed-on: https://gerrit.libreoffice.org/3627
Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>
Modules sal, salhelper, cppu, cppuhelper, codemaker (selectively) and odk
have kept them, in order not to break external API (the automatic using declaration
is LO-internal).
Change-Id: I588fc9e0c45b914f824f91c0376980621d730f09
- Increase the threshold for "dark" colours from Luminosity<=38 to
Luminosity<=60.
This makes LibreOffice align more closely with MS Word when
considering whether "automatic" font colour should be black or white,
a decision that is based on whether the background colour is "dark".
Beware that this also affects other areas.
- Fix the coefficients for GetLuminosity which appeared to be off
by one according to the "Rec 601" coefficients for Luma quoted at
http://en.wikipedia.org/wiki/Luma_%28video%29
Change-Id: I0af1f77909713e3db5ea8ee98456146569679594
Reviewed-on: https://gerrit.libreoffice.org/2601
Reviewed-by: Fridrich Strba <fridrich@documentfoundation.org>
Tested-by: Fridrich Strba <fridrich@documentfoundation.org>
Using the autocorrect list of LibreOffice
extras/source/autotext/lang/en-US/acor/DocumentList.xml
Change-Id: I8b93969bc0742c2e95b8b7db3c4c37691e8d3657
Script: http://pastebin.ca/2327716
Removed several unused methods.
Could not remove ScVbaFormat<ooo::vba::excel::XStyle>::getAddIndent() and ScVbaFormat<ooo::vba::excel::XStyle>::setAddIndent(com::sun:⭐:uno::Any const&) because it breaks compilation (they are implementing pure virtual methods).
Should Test::test1Table1Page() really be removed? (test class)
Conflicts:
unusedcode.easy
Change-Id: I98a761f66f28e3a82661c10a5fa1dc7e109fff2f
I ran the following code replace:
s/(Uni|Xub)?String\s*::\s*CreateFromInt32/OUString::number/
And finally removed String::CreateFromInt32().
Change-Id: I53b26a59c68511ae09f0ee82cfade210d0de3fa5
Reviewed-on: https://gerrit.libreoffice.org/2279
Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: Thomas Arnhold <thomas@arnhold.org>
Tested-by: Thomas Arnhold <thomas@arnhold.org>
...which has the necessary features to support it.
Change a lot of classes to either contain a protected non-virtual dtor
(which is backwards compatible, so even works for cppumaker-generated
UNO headers) or a public virtual one.
cppuhelper/propertysetmixin.hxx still needs to disable the warning, as
the relevant class has a non-virtual dtor but friends, which would still
cause GCC to warn.
Includes a patch for libcmis, intended to be upstreamed.
