Change-Id: I0e9a490ae4364b9bf14d6ad8766aef279a69db01

Change-Id: I2f55abf4526f4184ba04fc173df8cf5236219cfc

so it won't crash on exit when its dtor uses stuff destroyed by deinitvcl
already.

also fix comparisons, i.e. presumably
aLastColorTopLeft == aLastColorTopLeft etc
should have been aLastColorTopLeft == aColorTopLeft

Change-Id: I1f3dc47504c5add113b3a8bcadf010ca3b9f4c31

Change-Id: I1ec3d7845477cfb5bc6a3d7f70ddabef12583e1b

If that canvas contains a single shape, the result looks OK. If it
contains a groupshape, we also import something, but then the position /
size is still to be improved.

Change-Id: Ic4e4c08016a05a5e3acb005c3a642981ba4fb16d

These are just the minimal changes, so that writerfilter calls into
oox::shape::ShapeContextHandler, which does the real work.

Change-Id: Ia53731ac8592964b70e8a438ed09262463c05360

The plan is that once these are here, the writerfilter ooxml tokenizer
can refer to them. And then the writerfilter will call back to oox to do
the real drawingml import.

Change-Id: Ibc0d9838f3db717004a3bc8b80a408a39c8f0886

...the direct-initializations were introduced with
032d5126 "cppcheck: fix some uninitMemberVar in
configmgr part," presumably to avoid false positives from static analysis tools.
But the initializations are redundant, as the invariants of the affected classes
imply that the members have meaningful values at their points of use.  And the
direct-initializations with arbitrary values make it harder for a maintainer to
understand the relevant invariants, namely to ensure the members must have been
assigned /meaningful/ values by the time they are used.  Give a (subtle) clue by
making those into value-initializations.

Change-Id: Iadb25fa08b6d6b12d5bf8a8f04271270b6a7f7cb

Change-Id: Ice814ea226ddac24325770d038e019e19bc635ce

Change-Id: Ia2fe10af2ca555c7b88348e7ed571f1176586580

Change-Id: I93fa422afe7f3e1e10576dd64af9d57b2302f44e

Clang API doesn't provide this, but it's occasionally needed, and so far
the way has been inspecting the highest possible node in AST and walking down
and remembering, which is complicated, error-prone and annoying.

Change-Id: Id5b72cb5ebfc069e90efe6d673c0ef18ebcdab61

Change-Id: I0156c38e71fe46ea599a8366b953d429dfa424bb

Stupid me, I totally messed this up! God only knows how many non-bugs
people had to fix because of this typo.

Has the side effect of fixing fdo#64972 (among many others of course,
but this is the only one still open).

Change-Id: I9d8fdb6d37d4af9b0ac973902e469e0bd3a2408a

With the native AUTOFMT in Writer the SETATTR_DONTEXPAND does no longer
work reliably: if there is an existing AUTOFMT at the position then it
will be modified and no new hint with DontExpand will be inserted.

Work around this deficiency by inserting a no-length hint with the
preivous formatting at the end of the range.

(similar fix to the i#75891 problem in SwTextShell::InsertSymbol)

(commit 062eaeff did not
 introduce the problem but made it far more annoying)

Change-Id: I58ece7f5bd5a786b22a066e5902f1784dafa5dce

A suprising regression from 062eaeff:
The RSID text attributes that are inserted for every user-inserted text
cause the text formatting (SwAttrIter) to create a lot more text portions,
and the portion breaks make font kerning impossible.

This is the only way i can think of to fix this problem; alternatives that
don't work are splitting the RSID out of the AUTOFMT hint into a separate
one and combining them in the sw UNO wrappers (fails because
SwXAutoStylesEnumerator actually does need to enumerate every AUTOFMT
including RSID), trying to detect and ignore them just in the text
formatting (the SwAttrIter cannot easily/cheaply detect when it's allowed
to skip), and having an internal subdivision inside the AUTOFMT hint (one
subsection for every RSID change) (which does not work because it cannot
ignore RSID-only AUTOFMTs completely).

Solve the problem with 2 additional flags on AUTOFMT and CHARFMT
attributes: FormatIgnoreStart and FormatIgnoreEnd, which indicate to
SwAttrIter::GetNextAttr() that the start or end of the hint should be
ignored, so that effectively it is merged with the preceding/subsequent
hint.  Of course the UNO API does not respect the flags so we can store
the RSIDs in automatic styles.

The flags are maintained in SwpHints::MergePortions, which detects both
RSID-only AUTOFMT hints (which can be ignored completely), and the
situation of N CHARFMT hints + AUTOFMT hint vs. N CHARFMT hints +
AUTOFMT hint where the AUTOFMT hints differ only in their RSID attribute.

This means that MergePortions needs to be called more often now, in cases
where the ignore flags may have been invalidated, such as:
- insertion of text with possible DontExpand flag set on hints
- deletion of hints
- SETATTR_NOHINTADJUST mode

Change-Id: I1fb95a87c654c67d114f6f7f2c43b847c50b0ffa

This is annoying because it's not possible to use StartUndo/EndUndo
because that would break grouping via SwUndoInsert::CanGrouping();
also SwUndoAttr is somehow incapable of removing the inserted hints of a
grouped insert (it seems to leave no-length hints behind); so add an
explicit call to DeleteAttributes which should avoid the no-length
hints.

Change-Id: I1533daed9b2cf59886f380141b4eace4b22c15e0

Change-Id: I36ec7ad735fa15cfda88167b11a922883ef2bb72

we need to know that right from the start, not after the first
layout event after shown.

Change-Id: If7cc12cdf3e83913f0162fe34b376196162f6a45

(cherry picked from commit d70e1e8e)

Conflicts:
	sw/source/filter/ww8/rtfexport.cxx

Change-Id: I845f3f2bebe411969483a53c45ef9413f7f1b903

Change-Id: Ie2e126700540cbec2a94f40250b2a114d1ea9306

Change-Id: Ibcf081c0c64381e8c188764f036687a8bfc0ea0e

Change-Id: Ia53a9283fcb8f75386ec23ab3a3df5195a9995df
Reviewed-on: https://gerrit.libreoffice.org/4365Reviewed-by: Noel Power <noel.power@suse.com>
Tested-by: Noel Power <noel.power@suse.com>

Change-Id: Ic52fc416aea9d1ca7235613aed7cf494f17ae21a
Reviewed-on: https://gerrit.libreoffice.org/4361Reviewed-by: Noel Power <noel.power@suse.com>
Tested-by: Noel Power <noel.power@suse.com>

Change-Id: I91393aa912bd69f3fbeb67d895ff7d8021effccb

Regression introduced with 64e85a4c "Java
cleanup, remove unused imports."

Change-Id: I843cf651e20d2dd410f481222aca5206e0166a30

That rule was broken as it did not quote $@ which could be a pathname containing
"$", but it is unused anyway since 41efa153 "use
GeneratedPackage to deliver uno loader classes."

Change-Id: I4e5a15be8e4acca3d5be0c1b228f6c324d12331c

Change-Id: Ic93472b0621a13a777d37cfacc4230630f88a6ac
Reviewed-on: https://gerrit.libreoffice.org/4214Reviewed-by: Noel Power <noel.power@suse.com>
Tested-by: Noel Power <noel.power@suse.com>

Change-Id: I702509c7ad9dd3e84feb6d880264df36afe3c5b3

the "new" XDocumentEventBroadcaster

(cherry picked from commit 1bfae56d)

Conflicts:
	sfx2/inc/sfx2/event.hxx
	sfx2/source/view/viewprn.cxx

Change-Id: I6b3e1edc396b82d85fe059e6cdf7ad0009d5b94b

(cherry picked from commit 914cb68e)

Change-Id: Icb7c304b856cfca7f80090c2d193a0b92a27bb30

(cherry picked from commit 73a9e800)

Change-Id: I47975b23d7ef920de24f92d6ba12bae1233b2f38

Change-Id: Ic2cb501330b22227c05b303750152619c4b4abb0

Project: help  fd638f9abaea98e5a5f788b24faedc45fe01ec1e

Change-Id: Id1ded6828468ff956c83eb57f1da62fd80761b5d

This is a workaround for problems with file names containing $ in
gbuild. And it does not matter much in this case, because the classes
are never used during build, so there is no need to have exact
dependencies.

Change-Id: Ibeb30257a62ed13744dc4fe987830d1e5a4102b0

Change-Id: I09a76b4c6ad0e63663c2628e5ad957d203e0283c

Change-Id: Ib7f8aeeca64868fa2037145613023a6abfef7648

Change-Id: Ic0597f42b6f0a637e0a3fdfa7972cbe67272c65d

Conflicts:
	sw/UIConfig_swriter.mk

Conflicts:
	sw/source/ui/chrdlg/drpcps.cxx

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