Change-Id: Ic88b22895c2eb4144d31f22a0f7bc98971873262

Change-Id: I465e23dbe1d84a411c65500875a8821a116ecd2b

Change-Id: I76da768e035176c6469d9473364e9e2c9086ecae

...as reported by AddressSanitizer, where src/core/CLucene/index/IndexWriter.cpp
initializes IndexWriter::MAX_TERM_LENGTH with the value of
DocumentsWriter::MAX_TERM_LENGTH before the latter is initialized in
src/core/CLucene/index/DocumentsWriter.cpp.  But turns out that
IndexWriter::MAX_TERM_LENGTH is completely unused.

Change-Id: Ica01186584ec05a989a13dc58823f4751e8724e2

Change-Id: I9251488743ec3801367600455ef9a22ad876d2d3

Change-Id: Iaa80388952ac38a088874629688d9cf8a5fd456d

Change-Id: Ie5ccd62608c0643e3c8f019aea136ba74b282274

Change-Id: Ia980054437394ef48f7df655411f81d20b9cfa32

This reduces external link update time by 10%.

Change-Id: Ic14d9ea7530818f839330a2004f6aa67ef1e831e

Change-Id: I18520837f8d25103bf8482a0204b8a7b7740feb1

Change-Id: I5e34f4d7561ef7f4f7b8b3b4d7d06cca072831c7

Change-Id: I0ae2f44b89b0db915e78a9b07835000e843d016f

Change-Id: I983127828b28c72dd12d4778b88051964e9bceaa

This way, even after the loaded doc shells get purged due to timeout,
we won't reload those external documents from disk again.  One caveat
is that we currently don't pre-populate empty cells even if they are
referenced by the host document.

Change-Id: I1de2987836bf2fc5d9d7044b406fb99faa534164

Change-Id: I88b205d36eede5e63af46f8581896d980b6aa27d

Import especially when we have a whole bunch of large-ish documents open
in the background.

Change-Id: I614e6daab3481c09dae47c8407497d77aec40480

To prevent collision with the timer wanting to purge the doc cache
while updating external links.

Also, show progress bar, and make the timer interval and the document
cache life span longer.

Change-Id: I325984c8fa68425a2621cf8f9c016463291afc89

Rather than just clearing the existing caches and loading the external
documents on demand as the formula cells gets re-calculated.  This has two
advantages: 1) when the loading itself fails, we can keep the existing cache
rather than turning all affected cells to error cells, and 2) this prevents
on-demand loading after the external linkes get refreshed, which can make
scrolling very slow & painful.

Change-Id: Ie8243f6f94c5e477964413ab83f6b4b746fe3220

Change-Id: Ic309dbcc49a423bce10e9ea711e8ba0702552816

breaks the build otherwise on the baseline

Change-Id: I7a357bc9b541c86746ce3000af429ee024efeec1

The fun thing is that with the (only) call-site to ReadAsynchron in
PNGReaderImpl::ImplReadIDAT (vcl/source/gdi/pngread.cxx) passing in rIStm
references to stack-allocated SvMemoryStream instances, mpIStm could point to an
old, destroyed instance from a previous call, but which would have been located
at exactly the same stack address as the currently passed in rIStm, so the wrong
mpIStm->Read call would effectively behaved exactly the same as a correct
rIStm.Read call.

This went unnoticed "since the beginning" until AddressSanitizer's
UseAfterReturn check came along...

Change-Id: I7c75ed2d36a4c24c111d88eff647816bd2c5dbca

...(which can be called multiple times in a row).  But which actually looks
wrong...

Change-Id: I2e4914e6fed8ced383e430699dd462add9da8c08

Change-Id: Iebb19951efa81817793a155164862076d1198e6e

No need to create cached versions of stringified sheet tokens for
a given grammar at great for every formula that we compile; defer
until use. Is this a large cost on save ?

Change-Id: I8058ed564dbdc00ff45c02cb483c1a20a48af272

Change-Id: Ia394ff00421f495757cc2ce55e7b91bfebe715eb

Project: translations  b1ee9c9e1542b856cfe2412c6dffeeb5a353810a

debian packages don't cope with release number of 0, so use release 1
for debian master/dev-packages

Change-Id: Id91926322d13bddad3a39faccfee4e131d8956b0

Change-Id: I2714b1f1dadc74f8501203bc8b0722c56c9c5fb9

Change-Id: Ibe2f5f4ad52510247fb4134f433bba4b737d9c33

regression from e0284f4b

Here's the original code using the pre stl iterators.

if( !pPara && nDepth > 0 &&  rSet.GetItemState( EE_PARA_NUMBULLET ) == SFX_ITEM_ON &&
    pOutliner->GetDepth( (sal_uInt16) pOutliner->GetAbsPos( (Paragraph*) pList->First() ) ) > 0 )
	pPara = pOutliner->GetParagraph( 0 );  // Put NumBulletItem in outline level 1

Hidden in there is a pList->First() which only gets called if the prior
conditions are true.  pList->First() resets the index of the internal pList
iterator position of pList to 0 i.e. the next call to pList->Prev will now return 0.

The equivalent in the post-stl-conversion code is to jump the reverse_iterator
iter to the last position in the reverse view.

Create a level 10 entry in master view, select level 10, and use the bullets
and numbering dropdown from the side panel to see this crash

Change-Id: I52c22ea52020feb0fb75924f63ebe225be462071

...inadvertently left over debug code

Change-Id: I4bb9ee37ee7fd5d7e4e7f91afbcc036ba5802880

...and document how the member functions are supposed to be called from client
code.

Change-Id: Ia4847945e4a361c43a0ed001e3e78e901c9abcad

Change-Id: Id36f801cdf72d7654958b9d9837590990fdf161b

There are only 9 outline level styles, but we are allowed
(for some nutball reason) to create 10 levels, trying
to change the format of level 10 will then crash when
trying to apply its formatting to the non-existent
underlying style

Change-Id: Ic240322f98d832bc59edb502dd6d4988aa022481

Change-Id: Ie7919740e7e95eb53f7a719e3dc2b114c6fd3862

Change-Id: Ie691746b4621a90d2b7abbfbc75367780574032f

Change-Id: Ib77911177ec4d2f5b1f7c7ff75db30b6104f0682

Change-Id: I7662b77df94c439678d17fe31e611272d1802981

Change-Id: I4ad71bd3538b1d5b033802469b16dd35df5b9724

Change-Id: If7f39a1a0537c561373137e6a9dcdb22b48037f0