I guess the intention is to catch all "own" formats, and Base is just
missing from that list.

Change-Id: I064068c2ab17db9109a9a4681775ba8d18292292

If "EmbeddedDatabase" in test.odt refers test.ods in the same directory,
that will be "../../test.ods". Now if we save test.odt in a different
directory, we need to re-save the embedded data source definition,
otherwise the relative reference will resolve to a non-existing path.

Relative references are normally not supported for embedded objects, so
this is not a problem, but for data sources they are, that's why they
are a special case here.

Change-Id: Id138b9cdc38f2de589d9b80c66f1a61174699770

Change-Id: Ifc6471f58793cde057f354c4c6a549c073b7d34b

Modify createTestEnvironment so that it throws Exception. This
is appropriate for unit testing.
The wrapping adds no value and the calling method already has
a catch(Exception) to handle anything.

Change-Id: I430a414f63d2cbfc3b65ecfde0285509265e5192

This is more of the horror where the table in the frame has its cells out of
visual sequence, extend the previous fix of this kind to accept cells within
the original unmodified selected range

Change-Id: I6e8220f712fe9de5d4b98fb3cb5ed67e3762e929

Change-Id: I76d50a135153a7022b481e4025f9b5f948ce7efa

Change-Id: Ia16c1ba6052e8cf86762be095930b7e748f4493d

Change-Id: Ic33ee6936f40bec4f3a82aea39a180ae6e9a0928

Change-Id: If0c56c89e2722d47a401363f3854331229856490

Running e.g. CppunitTest_sw_ooxmlexport under UBSan revealed problems with
SwBorderAttrs instances with dangling pOwner pointers, which caused bad memory
access during exit when ~SwCache calling ~SwBorderAttrs tried to use pOwner.

The problem started with a4dee94a "tdf#91260:
allow textboxes extending beyond the page bottom" (and hadn't changed with
follow-up 2f779fc0 "tdf#91260: cleanup -
textboxes extending beyond the page"):  The call to

  pFrameFormat->SetFormatAttr(aSize);

in SwAnchoredObjectPosition::_ImplAdjustVertRelPos ultimately calls
SwCache::DeleteObj on the SwBorderAttrs instance that is locked by the

  SwBorderAttrAccess aAccess( SwFrm::GetCache(), this );

down the call stack in SwFlyFreeFrm::MakeAll.  That means that
SwCache::DeleteObj will return early without doing anything (apart from
triggering the OSL_ENSURE "SwCache::Delete: object is locked."), leading to this
leftover SwBorderAttrs instance causing trouble during ~SwCache.

The scope of aAccess in SwFlyFreeFrm::MakeAll had always extended well past the
uses of rAttrs (= *aAccess.Get()), covering also the

  if ( !mbValidPos )

block (that contains the call to MakeObjPos leading to the call of
SwAnchoredObjectPosition::_ImplAdjustVertRelPos), ever since
84a3db80 "initial import."

With cb19042f "New feature: vertical alignment
for text frames: Layout part," an additional use of rAttrs (in
MakeContentPos( rAttrs )) had been added after the block calling MakeObjPos.

The hope is that (1) it is OK to release aAccess earlier, after any (original)
uses of rAttrs, but before the call to MakeObjPos; and (2) it is OK to just set
up a second aAccess/rAttrs for the later added use of rAttrs in the call to
MakeContentPos.  (That is, to punch a hole into the aAccess scope, so that
ultimately SwCache::DeleteObj succeeds on a now-unlocked SwBorderAttrs.)

Change-Id: I7cb9919b1c9d7c87464ac3a0fe1edfed5b46e122

Change-Id: I1eae8c96c12ba4d272341f45fee6c1fd66ab9e28

Change-Id: I9f533f577f959c9a715e5214be99ca59cb0d206c

Change-Id: I06dae2e7a5067160326f4c65f5975c4e5afb05ce

Change-Id: I27da86c774f0450c844e742563c4a8de3f23ad34

Use G_GNUC_CONST that adds const function attribute to
lok_doc_view_get_type() for better performance.

Change-Id: Id79f0395a98c4f98b46303e9b5ee1e103fbe331f

Change-Id: I3bbd07ce8163890f9b88567966622dd4fbe9d94d

If we are mentioning this type as DocView, we should break it at each
capital letter.

Change-Id: I76c7eea455281e541b2196a03778018aa127cebe

Change-Id: I8c60c9ba13516fc2b3a926c19b41ee19805d74a5

Change-Id: Ib33f0e1dcf257350be1e2cf6c49cd92494472a55

... and place it at places only where the widget can change its size.

Change-Id: I4a4b28b35eba06a6faab434677d4d70d2a33339a

Lets follow the old advice: "Be liberal in what you accept, be strict in
what you produce".

This is after noticing negative values for x, y in
the payload in some situation, such as, hitting a backspace key when the
cursor is at the start of a line

Change-Id: I11939b981f75969b88214baee66b4c69c5e41906

Change-Id: Iaf4a5fba5c4c34d03b91ca9ca4dd4eff1dbf39f6

Improve documentation, style fixes

Change-Id: I5000e32e90cd8e3b75e8df2907673efc303a55fd

Lets use a member function to set invalid tiles that come under the
given GdkRectangle.

Change-Id: I440336ddf3c5fd9094f35bb89479aa76a42477fa

twipToPixel and pixelToTwip are also being used by the new TileBuffer
clsas. Lets move these utility functions to a common header,
tilebuffer.hxx

The variables for DPI and tileSize are also moved to tilebuffer.hxx

Change-Id: I9d0bec7f2aefe412df232040a7a9abc6db3e4ccb

Change-Id: I8637d99e6fa59129af207e667bcdf03dc212efeb

Using vector each tile needs to be allocated memory irrespective of
whether tile is required or not. This approach fails when we zoom in to
a very high level to have thousands of tiles due to lot of memory
required. Using maps instead of vector takes care of this, and only
allocates Tiles when required.

Change-Id: I523f815618451a7f014e28258e0de7b1c0693370

The TileBuffer class now manages all the tiles. The tile rendering calls
to LO core is also managed by this class.

Change-Id: Ic667a93dcf1c097e0601c0496e8a083c4742e8cb

Change-Id: I1a3d8a9229f416418f0f3e9c720b78af09b35978

Change-Id: I64212113750893f33f8a859ba52ecd8815a820f4

clang plugin

Change-Id: I1392ad1834dc590cec12e379d6478c42b1bbbc20

Improve the plugin a little.
Create a python script to process the output.
Run it again.

Change-Id: I05c21d8a21c8f4243af739c412fda0a521f9b5f0

From Alexander and Adwaita.

Change-Id: Ib3f396ab2cbb0a89da00a7f8634fc6fe6be0b223

Change-Id: Idf1bfbac1adc083f6d697d19ca41110f765955e9
Reviewed-on: https://gerrit.libreoffice.org/16171Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Andras Timar <andras.timar@collabora.com>

But actually I strongly suspect that this is dead
code.

[AquaA11yTextWrapper rTFForRangeAttributeForElement:forParameter:] is
called only from [AquaA11yWrapper rTFForRangeAttributeForParameter:],
and that is not called from our code, nor do I see any mention of
either rTFForRangeAttributeForElement or
rTFForRangeAttributeForParameter in documentation or when googling.

The NSView documentation does talk about accessibilityRTFForRange,
though. Could this be some copy/paste error since initial commit, code
that has never been tested? Would not surprise me a bit.

Change-Id: Ia1351c293e51e0b75d8b222f78ea19f7801a7c18

I also have done the extension and the help icon according to galaxy.

Change-Id: I1f1dcce9c4a7aa1609d039381b4f85cf9a8b6f37
Reviewed-on: https://gerrit.libreoffice.org/16176Reviewed-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>
Tested-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>

Change-Id: I985ac3eea9ebb780821ab4fffd460935be5e536d

(regression from 587006ca)

Change-Id: I38e00a7469243088e25aa1a91e3581240b3bbdea

Change-Id: I66e69de20e45509de10bc6fe72d0a81bd4805647
Reviewed-on: https://gerrit.libreoffice.org/16168Reviewed-by: Matteo Casalin <matteo.casalin@yahoo.com>
Tested-by: Matteo Casalin <matteo.casalin@yahoo.com>

Change-Id: Ieedf4810f1e726bf11f0d0b1a203e560a0b16550