Change-Id: Ie84fe35db0dfca08e2b270636f06bef90c1455ab

Change-Id: I15ae1693e92e430c78b5d73c12a7bae297c098bb

Change-Id: I9614e1495e6d990e050c651c2aed0ba0e43d51fe

Change-Id: I0f617f2b4ef7bcb2b07295223acae5519280a41e

Previously, the timer events could have accumulated in that scenario leading
to unresponsiveness to user events.

Change-Id: I455d726ae7475f7dbf98d871c54d8c156cb64e52

Change-Id: If0da6e0e34ce50bbe7dceda089b6bb81b4a63f36

Regression from e8bdd388
(fdo#83751-FILESAVE:Custom Properties dropped while exporting to .pptx,
2014-09-11), there were two problems here:

1) Using the wrong filter when the output is expected to be suitable for
validation.

2) Writing empty custom property values, which is not valid.

Change-Id: Ic18c789c53bd40cc8aa07385cb5fd0d5c7ada6ab

Just seen a test with a null m_xHandler, no idea how that happened.

Change-Id: I2e5ff9d3c799284beea5fdca37fa8a825f8a4756

The timer callback SalTimerProc can be called after DeInitVCL has
deleted the SalInstance, and crash.  Avoid that by calling
WinSalTimer::Stop() and also using the INVALID_HANDLE_VALUE parameter
which waits until the timer callback is done executing.

Change-Id: Ia4cf2cf9dc48904d077e0a691e14107256c50ded

... and no, we do not "overload" virtual methods.

Change-Id: Iff7c46326974995994e966873ff804092bc53540

Change-Id: I28f2f4bc3c43aac1faf8be35cf7ce89480487102

Change-Id: If5a04b7b9ab6c7909cf089f7e935f9c08ea31948

Change-Id: Iacd1c0856f991e11ef26d7ff6bf1e75264b89ac9

Change-Id: I9c56dbee65c93dd98344577d9e696dc61c1edbd8

Change-Id: If4de88233493d7590736e4a3b76c2447ed429ae5

Change-Id: Iecf69c29a4574105a33ec003970067d4db823423

in favour of a wrap property on NumericField

Change-Id: I62c6bdb69a16f37ae6018a2fe41070fb18dbe4a0

Change-Id: Ia88671cb71a0bcf8cb55ae0d88625b0f28092615

Change-Id: I60cfe651a6ec25fc7e482192d908acca25c1ad8b

doesn't matter in practice

Change-Id: I410022a395d25827217b9c542d79718f6f5b333d

Change-Id: I7a225287c9ca2f14d2e8da15380c541148d1a15f

Change-Id: If110d27950a4efd1a96dc5f2702f4dfbfe58bcbe

and

coverity#1210001 Uncaught exception

Change-Id: Ia6ef659ba6e62d56813a87c3fcf0fa4a5d26d9f9

Change-Id: I53ace3f34036f2c78201aea7fb4a4a2e7c750654

http://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/149

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

Change-Id: Ibeab8e1b64f3185eaca81a31bd131d11994386f3
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>

A plugin to warn about and rewrite null pointer constants that are not written
as nullptr (in C++11 code) resp. NULL (in C and C++03 code).  It is not
activated for the following reasons:

* At least the call to

  pImpl->aFmtNms.insert(pImpl->aFmtNms.begin() + nPos, nullptr);

  in svx/source/items/clipfmtitem.cxx would require
  <https://svn.boost.org/trac/boost/ticket/10540> "missing std::nullptr_t
  support in boost/type_traits/is_pointer.hpp" to be fixed first.

* Additions of code that violate the plugin would probably be frequent, causing
  unnecessary grief for those building with plugins enabled.

* It did not find anything interesting, apart from the above Boost bug and the
  mildly interesting 1da153b6 "Consistently use
  APP_WRITER as an integer, never as a nullptr."

Anyway,

  until make -O -j4 -k check; do make -O -j1 -k check \
    COMPILER_PLUGIN_TOOL=nullptr UPDATE_FILES=all; done

sucessfully executed on a recent master and resulted in

  6798 files changed, 60919 insertions(+), 60919 deletions(-)

Change-Id: I1260227949868e73fcb63fda13d83e79fde685d7

Change-Id: Iabc76b3e78afa491a38fa04d648f48f15ac3870e

At least test Unix platforms.

Change-Id: I960343cb9622474fe48687a5e458e1c6dbe55358

Change-Id: I83fb0462c662e0da1f1c5c6dfec4bd8d94d97b87
Reviewed-on: https://gerrit.libreoffice.org/11420Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>

Change-Id: Ic4b8acfc3cbd8c86b765a950d61742c229f3fb6d
Reviewed-on: https://gerrit.libreoffice.org/11390Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I25e3599a37d720cbcf70ea13ab30234e54637d53

Reviewed on:
	https://gerrit.libreoffice.org/11639

Change-Id: I0852f9766495379b0208e236b3cbeafde5bf07b3

This also improves positioning a bit, in the changed testcase the
perfect position would be 211.663888889, and reality is now 210 instead
of 208 (100th millimeters).

Change-Id: I5226f2165224a8bbfebfd11d9c612f72d83b8c69

As in the ticket description, this test is now working, but
some parts of it are still commented out, because they are waiting
for a fix of another bug (Bug 84237). Once it is fixed, it should
be possible to just uncomment them, and then they should work.

Change-Id: I73d1cc7391080e357c08cb3442616e2901070c1f
Signed-off-by: Stephan Bergmann <sbergman@redhat.com> (with minor amendments)

iow, allow opening Impress and Draw ODF documents read-only

Change-Id: I379b9f92b9bfb20e99998177d9a5fae80069d98f
Reviewed-on: https://gerrit.libreoffice.org/11495Reviewed-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
Tested-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>

Change-Id: I75267bf44d0fd36ff316f59300efd31524da36ef

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

(not that it matters much in practice, on platforms where nullptr is all-zero
anyway)

Change-Id: I640e4e3e8c77f8c5c59c8e4b51c04f72dc1fadf9

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