[ Miklos Vajna: The point of the change is that without this, part switching in
Calc does not work, as Calc does not invalidate everything after a part switch
(unlike Impress), and we suppose the right fix for this is to let the clients
throw away the tiles, rather than letting Calc send out invalidations, too. ]

Change-Id: Id368b955c54efb87ecf3d59278ddb5cdbb2e7856
Reviewed-on: https://gerrit.libreoffice.org/17267Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Commit 0208ead7 (DOCX import: improve
btLr table cell support, 2013-02-22) made any table row that has at
least one btLr cell fixed height. This causes problems in case a table
has a minimal height with lots of content, where the fixed height gives
wrong layout, but the minimal height is correct.

Fix the problem by only making the row fixed height if <w:cantSplit/> is
set (as seen in the old bugdoc), and revert to setting the height type
to minimal in any other case.

Change-Id: Ibaf91f542e64e5caa7904df97eb6eb52618e0023

Change-Id: I0016aefce1aad3a89bd23dcec6fbab58a7c844d7
Reviewed-on: https://gerrit.libreoffice.org/17263Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: Ib95638267c5a7df73ccdd179dd62ac7c9a53a5e4
Reviewed-on: https://gerrit.libreoffice.org/17262Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: Ifdc1b8e561e69947b1458aca691cb974071715b5

Not all yet, though.

Change-Id: Ic4f0fe3ded31d585faefd8bda8ab87f54b88dc6c

Change-Id: I397566ae2488799399cad361b24a281d3599cc5b

This is an odd-one; lots of details in the bug.

Change-Id: I287945eba965cc637642e9226c7fe7f2a0754130

seeking resets eof, so the IsEof is always false
after the first loop

Change-Id: I2e533f3f9c494566aabb947c05258a770e883b1f

a special case for INDIRECT function interpretation. Does what
OOo used to do, interprets formula using CONV_OOO first, failing
that, tries CONV_XL_A1

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

Change-Id: I794cc4de0fb35dc5471c15873649712f03178817

Else, on any action done directly (not through the
FormControllerHelper) on the controller and raising an SQL error, this
would silently swallow the error message, and the operation would fail
without any message to the user.

E.g. when validating an insertion or modification in a grid control by
moving the cursor to a different line (as opposed to clicking the
"Save Record" button).

Change-Id: Ie569d9c826609f803f7b312c0469907155558ef2

Change-Id: I727c5af7659e9591563c0784fee5d0d9317ebc24

This avoids arbitrarily switching to the first form in the document,
which would do a (premature!) save to the database of the
modifications pending in the active form. This may lead to a database
error, when the data is not in a shape to be written to the database,
e.g. when on an insertion row and not all mandatory fields have been
filled in. This then pops up an error message to the user.

Change-Id: I30bb533598ca707b892bb7155e54ce05d4ddf275

Change-Id: I534480411d6c164f9f0955933b612c1a219402fd

We're dealing here with 2 bugs:

1. Single shape buttons (like rectangle, ellipse etc.) don't get
   the pressed state when active. The cause is that all commands of
   the same kind (Basic Shapes, Symbol Shapes etc.) are handled as
   one internally, allowing only one type of status updates. It used
   to transport the current active shape, but it was changed to a
   boolean value in the fix for i#41753, and since then used for
   the pressed state of the group buttons.

2. The pressed state of a group button shows always, even when a
   user activates a shape from a place other than the drop-down
   of that button. But in this case the image of the group button
   doesn't update with the current shape, thus confusing the user on
   what is currently active. The cause here is that we use (since
   i#41753) the XSubToolbarController interface to update the last
   selected function (instead of the old-style status based update),
   and ToolBarManager notifies a controller about a new selection
   only if it was made from a particular toolbar that the controller
   claimed to use in the getSubToolbarName method.

   Since 7352a7c1 there is a similar
   regression for other group buttons in sd (like lines, 3D Objects
   and other), with the same cause. This is also fixed now.

Change-Id: Ida074a001ff78bf5bd5bcb8151516daa6e27cbce

Change-Id: I6fff5af5d623bff6f8adedf6f3d42d849ea4d24b

tdf#91278 related

Change-Id: Iab4728b07649bcbb1beb372e68369f3762b13a5c

Change-Id: I7885f8ba5ec4c6e60d88f6caab0c25cb760529ef

Change-Id: I4b4b263f4448c4d3b83cea57635624b31f757576

Change-Id: Ia770e7a6a7ebcc875f3cf94471dcc032aeadc2d7

Change-Id: I6d526440bd652dcd1745b8d84ff69855691d7e48

Change-Id: Id04343aa5de0caa5b066d7fbd2fa97b670f5cf54

Change-Id: I78856512069afa653b374f3d4b79db7307743294

Change-Id: Ied51535fa169451fc4991237122817a34a59f6fe
Reviewed-on: https://gerrit.libreoffice.org/17256Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: I388f191fecd5f1d632f1540d280a04c163ce6fc9

Change-Id: I741c5f5ed895b06a445f42e20ef004a8c7c1a100

Change-Id: I287d99a46eda90718a3c4ec2c92f7b063babeb24

Change-Id: Ie67518536932e24e9cff7a8b75b42e90e9f67673

Change-Id: Ia475ce737c430fab8d019e1b8a762f81897e0847

Change-Id: I5187364d420ab78c36a91632efab9c32951d867a

Change-Id: I64e77f12cb016a7f4a9d21c732aaeaae7959da76

Change-Id: I9b5399ace50db3259df2e619f28ae547a38e6c6d
Reviewed-on: https://gerrit.libreoffice.org/17254Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: I810cdadedd5261caede474a4780ceea6d9b409c9

Change-Id: I52441115e14da6c1bcd7ba4926a0f3cc0620366e
Reviewed-on: https://gerrit.libreoffice.org/17236Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: If877cd61000fe6b82083a9fff79c25364d49e721

Change-Id: Ia7cc48f6f1bc041b95164d551e2cbc9ea2dbf2e8

With this, not only the definition, but also the declaration of e.g.
'SwTextFrm::Format' (or any other member function that is overriding a
virtual function from a base class) can be found again, just like before
SAL_OVERRIDE and the similar macros were introduced.

Change-Id: Ic9e429ad7cbb0a1212744115d1567bb79b7c6aa0

Commit c1f8437d (fdo#83465 RTF import:
handle font of numbering, 2014-09-25), changed the "get the me character
style of the current numbering's current level" member function to be
successfull even in case we're inside a DOCX run, not when we're inside
a DOCX paragraph, but outside runs.

While this is necessary for RTF, the side effect of this was that
unwanted run properties started to affect the above mentioned character
style in case of DOCX.

Fix the problem by enabling the "in paragraph and run" looking for RTF
only.

Change-Id: I610bfce6cec15b918fe547402360f5a894401f7e

This allows them to be used as set members and dict keys

Change-Id: I10bd71788be6b508c6f491a27a8841e599e47e3a
Reviewed-on: https://gerrit.libreoffice.org/17248Reviewed-by: Matthew Francis <mjay.francis@gmail.com>
Tested-by: Matthew Francis <mjay.francis@gmail.com>