Change-Id: I2821969d86b7f8cee53404e6a0acfbebbe53b3ac
Reviewed-on: https://gerrit.libreoffice.org/39824Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

Change-Id: Ib00f60c8018e025f9d5955784b31f3110b4e40eb

which is considerably faster if we're dealing with a std::list, and just
easier on the eyes if we're dealing with a std::vector

Change-Id: I373689205ebc048689f29ab80a7ee8551b20cc96
Reviewed-on: https://gerrit.libreoffice.org/39816Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

Change-Id: Ifa150dc9d694981ffe03c254ea8c3fd820c99795
Reviewed-on: https://gerrit.libreoffice.org/39812Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

was only in two places, and did nothing to make the code simpler or
easier to understand

Change-Id: I8e91d7e00f14a0611bf563a855d616ad11da5342
Reviewed-on: https://gerrit.libreoffice.org/39813Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

Project: help  0f9722866caf9d5175df3e49170f40b9567f0c16

Help-in-browser (viii) more...

* Correct schema
* current set of built languages.
* https://helponline.libreoffice.org

Change-Id: I887214b080e6200ac840b74d175292649f8e4298
Reviewed-on: https://gerrit.libreoffice.org/39836Reviewed-by: Olivier Hallot <olivier.hallot@edx.srv.br>
Tested-by: Olivier Hallot <olivier.hallot@edx.srv.br>

ALT+up/down behaves differently inside a table: cursor is moved
to the left/right neighbouring cell instead of up/down. However
when the whole table is selected a different behavior is expected:
moving the table as an object.

Change-Id: I82c7a3cc7d215b21f19fbf08dcdb7318a7e75289
Reviewed-on: https://gerrit.libreoffice.org/39810Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Tamás Zolnai <tamas.zolnai@collabora.com>

Author's Enter key must had been broken as well, not only Space key..

Change-Id: I61c947a988f36cb55d1037ca0bd277fca181b09e

Change-Id: I68ffa3f79df0acf484868c13817d76582edd7a41
Reviewed-on: https://gerrit.libreoffice.org/39790Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>

Now that ScCompiler compiles ScTokenArray we can finally handle
FormulaToken::IsInForceArray() as well.

Still missing is the evaluation of the selected sub expression of a formula.

Change-Id: I801859498569e4369db13144fe8ba08ca576350b

This reverts commit ff10bc47.

    commit ff10bc47
    Date:   Tue Jul 11 10:24:51 2017 +0200

	loplugin:casttovoid

	...as introduced with f6574be0
	"FormulaDlg_Impl::MakeTree: pass down current function/operator token: In
	preparation of better argument evaluation."

That (void)pFuncToken was there to not break the build with unused parameter..
and all work in progress.

Commit actually using pFuncToken follows immediately, I'm just too lazy
to resolve the merge conflict for an already ready patch.

Change-Id: I572c3087a1cca9efa217e1e1818192d251e3345d

Change-Id: Ia99f3b4a8c9aba506938b8c3669c74b5dc1b4c16
Reviewed-on: https://gerrit.libreoffice.org/39122Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>

So this actually obeys all application specific rules when generating RPN code.

Change-Id: I5e1a89efffe5188d3c4b68176cc410a6cd76483a

For application specific derivatives.

Change-Id: I8af95bd120c642e47ec5d0708ed463c98c471567

Change-Id: Ia8bd4ead67183e7f56c804e949ac04c6451c5201
Reviewed-on: https://gerrit.libreoffice.org/39809Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jochen Nitschke <j.nitschke+logerrit@ok.de>

Change-Id: Ie8570de6a4eafc95352899fbfd1447d7c3a84e1a

Change-Id: I309f98f6b820103a926e9fe94d67d0aff6eb6476
Reviewed-on: https://gerrit.libreoffice.org/39754Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

Project: help  551a5fdaba7c7b86b41daafd4574e7b1649c11d5

Help-in-browser (vii)  more improvements

see it in http://helponline.libreoffice.org

Added mos keywords from schema.org
New, responsive page design

Change-Id: I9df963c1a962c0fbb5c2926d8066b31cd20d485b
Reviewed-on: https://gerrit.libreoffice.org/39822Reviewed-by: Olivier Hallot <olivier.hallot@edx.srv.br>
Tested-by: Olivier Hallot <olivier.hallot@edx.srv.br>

Follow-up to commit 78d1f1c2 (fdo#68607
bnc#816593 DomainMapperTableHandler: don't always start a frame,
2013-09-03), turns out in case there is little space between the table
and the edge of the body area, then there is no wrapping performed in
Word, so we should not convert to floating table, either.

The limit seems to be 266 twips (mm100 unit is used in the code), and
this seems to be constant: it does not change if both the table and the
page width is changed, nor does it change when the empty paragraph to be
wrapped has a different paragraph mark size.

For the majority of the documents this means no change as usually there
is either no space available for wrapping or there is a lot more
available.

Change-Id: Ibbf7409065ba958854514f23b360be56677c8fe3
Reviewed-on: https://gerrit.libreoffice.org/39808Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Jenkins <ci@libreoffice.org>

Change-Id: I50c8697d51c480c668c66a1cdc2c670575a1ec37
Reviewed-on: https://gerrit.libreoffice.org/39804Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

and merge together checkSeeks

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

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

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

Change-Id: I20318c77dcc3bc2a64336541ef5a3f412bfd9483
Reviewed-on: https://gerrit.libreoffice.org/39803Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

drawingML shapes are independent, and having a separate parser for each
shape is a good thing, so that when we have an XML fragment like this:

<wps:wsp>
  <wps:txbx>
  ...
  </wps:txbx>
  <wps:bodyPr .../>
</wps:wsp>

where <wps:txbx> may contain nested <wps:wsp> tags, we apply the
properties specified in <wps:bodyPr> to the correct shape.

In contrast, doing the same for VML is not a good idea, see commit
476316bf (do reuse shape context,
2012-05-22).

So conditionally (for DML) maintain a stack of shape parsers, this way
the outer <wps:bodyPr> is parsed and the result is applied to the
correct shape, at the end resulting in correct inner margin for the outer
shape in the bugdoc.

This requires moving the context setup code from
the OOXMLFastContextHandlerShape ctor to setToken(), as only then we
know if this shape context will be used for VML or DML purposes. This
should be OK, given that
writerfilter::ooxml::OOXMLFastHelper::createAndSetParentAndDefine()
calls setToken() right after allocating the context.

Change-Id: I8c0d2f49cac76589fe269230698b203b5ca6996c
Reviewed-on: https://gerrit.libreoffice.org/39798Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>

When working with pivot cache there's alternating use of
locale dependent and locale indepentent formats, which
causes unnecessary loading of calendars due to constant
switching.

OnDemandLocaleDataWrapper already does this, now do
something similar in OnDemandCalendarWrapper.

Change-Id: I3d64dbe8afa929cf416d87678762e82b45561d63
Reviewed-on: https://gerrit.libreoffice.org/39762Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
Tested-by: Noel Grandin <noel.grandin@collabora.co.uk>

Change-Id: Ifa228ca02ea79a1309e1875414028aade7e5f12d
Reviewed-on: https://gerrit.libreoffice.org/39801Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

it prevents creating unnecessary expanded shape hierarchy and allows
layout algorithm to know parent's size

Change-Id: Ieb991a74bd662e359f5cf479a7480893e0b13d45
Reviewed-on: https://gerrit.libreoffice.org/39410Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>

Change-Id: Ifad32425d79be5a22d33d721bdc5fb993f699759
Reviewed-on: https://gerrit.libreoffice.org/39763Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
Tested-by: Noel Grandin <noel.grandin@collabora.co.uk>

Refactoring codes that cast XFastAttributeList reference
to FastAttributeList pointer using the helper function.

Change-Id: Iecf4b815d6556b0992d638b633260fbd459c0dc4
Reviewed-on: https://gerrit.libreoffice.org/39723Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>

Change-Id: I233c84706916bfe3915e31deb8d41b3b377b7d98

3  in () at /lib64/libc.so.6
4  in VclPtr<AbstractSvxHpLinkDlg>::~VclPtr() (this=0x88d47e8, __in_chrg=<optimized out>) at include/vcl/vclptr.hxx:115
5  in SvxHlinkDlgWrapper::~SvxHlinkDlgWrapper() (this=0x88d47a0, __in_chrg=<optimized out>) at include/svx/hyperdlg.hxx:34
6  in SvxHlinkDlgWrapper::~SvxHlinkDlgWrapper() (this=0x88d47a0, __in_chrg=<optimized out>) at include/svx/hyperdlg.hxx:34
7  in SfxChildWindow::Destroy() (this=0x88d47a0) at sfx2/source/appl/childwin.cxx:182
8  in SfxWorkWindow::RemoveChildWin_Impl(SfxChildWin_Impl*) (this=0x6c83940, pCW=0x683bc20) at sfx2/source/appl/workwin.cxx:1425
9  in SfxWorkWindow::ToggleChildWindow_Impl(unsigned short, bool) (this=0x6c83940, nId=5678, bSetFocus=true) at sfx2/source/appl/workwin.cxx:1832
10 in SfxViewFrame::ToggleChildWindow(unsigned short) (this=0x6afdae0, nId=5678) at sfx2/source/view/viewfrm.cxx:2964

Change-Id: I84a1ba817dc8449dc1942b6ebd443ec955e8c622

Adding fullscreen presentation mode.

Change-Id: Id07416ce204d1d7dd917fbd33a4d9f5072ac1703
Reviewed-on: https://gerrit.libreoffice.org/38006Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Tomaž Vajngerl <quikee@gmail.com>
Tested-by: Tomaž Vajngerl <quikee@gmail.com>

...as introduced with f6574be0
"FormulaDlg_Impl::MakeTree: pass down current function/operator token: In
preparation of better argument evaluation."

Change-Id: I2ea39115bc2d2dbbea6fd899c347c98949ec281a

Change-Id: Ia585572c911a268f68e611935a1d5264dd0790c5
Reviewed-on: https://gerrit.libreoffice.org/39504Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>

Change-Id: I6ea2cf715095e5f686fa8a4262682553e9a293ac

Change-Id: I99864b43f3b54eefbb80a885b701838b3e27d806

Change-Id: Id265092c1cbf09f8c29c77c048edbf14f15070eb
Reviewed-on: https://gerrit.libreoffice.org/39515Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Chris Sherlock <chris.sherlock79@gmail.com>

The UI for placing a frame in the background is confusing because:
-in menus, the icon looks like a checkbox, but functions as a radio button
-it isn't obvious that "in background" is the opposite of "wrap through"
-it doesn't act like the checkboxes below it like "First paragraph"
-in dialog boxes, it is actually implemented as a checkbox toggle.

So it looks like a checkbox, and you can enable the checkbox, but
once enabled it can never be disabled.  (The currently designed way is to
select wrap off/page/optimal/through in order to disable in background.)

This patch creates FN_FRAME_WRAPTHRU_TOGGLE to replace
most uses of the previous function.

Change-Id: Ia46ddbd47899e8ca569bf3adb2b1c4ad7cfa1920
Reviewed-on: https://gerrit.libreoffice.org/39673Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Heiko Tietze <tietze.heiko@googlemail.com>

Change-Id: I3a82c43e80fffb4bf37bb2f7a3f5b3b26f1baf98