seek resets failures, need to check after a read
and before a seek

Change-Id: Ia249e258c51af5efc838f92c4ead6237b403c701

takes the last token in case of chained "." instead of the first one

to avoid

aa.b.
autocorrects (wrongly) to
aaaa.

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

Change-Id: I5790c949354434fc3661520c9038fd90e1b182f4

Change-Id: I8d44cca45340bc6c204308cef7e17907ea7a7c67

Change-Id: I7bb930f3b062dda9e46f517a1ea1dacb0d64de7f

Change-Id: I98f8df3f27fbd520f0bfbbb39c0e3cc5fa892b0d

and improve the error message in the plugin

Change-Id: I8719832a48e14c132f463340fbbc537845f82b0b

find places where we should be using std::unique_ptr

Change-Id: I5b9defe778fdc4738ecea381215396874db59e66

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

Change-Id: I2148fd9953b283945d2a1bcf24dbc47964b659ae

Change-Id: I1ae96c7b6adf5a90f96d7dddc20d7fb241e78445

Change-Id: Ibf62ffa133aa4cde1836f7b7e735559c02ffb588

Change-Id: I689d84ef58faeb4b36159c6370b5e97a13d39736

Change-Id: I631120903f15256997e082e0d079da7c5ee9944b

Surprisingly SvtMenuOptions_Impl::ImplCommit() does not actually write
m_eMenuIcons for "ShowIconsInMenues" but something read out of
Application::Settings(), which appears to be deliberate (i#95318).
Whatever sets that does it after SetMenuIconsState() is called,
so keep the SvtMenuOptions modified by not calling Commit().

(regression from 765f6211)

Change-Id: I368b65589d16753d80a1b9e9cc7d7df59c0f53da

Change-Id: Ib45a02248819c35844ef83435c33ab1c82f5c4dc

This implements the basics for that and implements it in the AreaPanel.

Change-Id: I6d9e5012bbcc2c953d478a09a839f35f2ef64c5b

Add a move constructor and move assignment operator for
o3tl::cow_wrapper. Insubstantial gains for UnsafeRefCountingPolicy, no
atomic increment needed for ThreadSafeRefCountingPolicy's move-ctor.

Change-Id: Ia2de1ca78b1e0e5a0f30535e752f1dd858fdfef0
Reviewed-on: https://gerrit.libreoffice.org/17848Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>

Change-Id: I966069726fd7dbc57e03e93514bec62d8bbb2ba0
Reviewed-on: https://gerrit.libreoffice.org/17862Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I2a56ebf8edb30b5f16e09237f9480484a699170e
Reviewed-on: https://gerrit.libreoffice.org/17861Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I93bdb33a442a358b0067d57499b11d73bfbaa2d9
Reviewed-on: https://gerrit.libreoffice.org/17860Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>

... for the PythonTest, similar to what vclbootstrapprotector does for
CppunitTest; actually no idea if this is a good idea or a bad idea.

Change-Id: Ia4e2e50fdc9c8deb9faf580a2f3f3308533265eb
Reviewed-on: https://gerrit.libreoffice.org/17540Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I83396e7c90d3b182f353a77c9bdf06fd17af92a1

regression from

commit b3abc191
Author: Laurent Balland-Poirier <laurent.balland-poirier@laposte.net>
Date:   Wed Jun 17 15:15:07 2015 +0200

Change-Id: I44cfd85e9f7be65929281169fd297252e00c7317

Change-Id: Ib93b818eeebc2f370535d1b061beabf7e8c65257

Change-Id: I39295d69dd8a48f0f40275830cb6fda4ca0b69f3

Change-Id: I55848b3fedae79d714c8341fd84d505cb83a7c2c

Regression of ece8699f

Change-Id: I1aac18dcb469b30de625c5cbfb5b0dd27fe33364

Show the whole height of the cache bitmap after all (when SAL_LOG
contains vcl.gdi.opengl). The interesting pieces are often at the
bottom, like the tip of the hook of the "j" glyphs that used to bleed
over into the preceding glyphs, usually "i", when they were rendered
into the same chunk.

Add more space between glyphs and at top and bottom of the bitmap, for
anti-aliasing. The glyph ABC widths don't take expansions caused by
anti-aliasing into consideration and are misleading. Hopefully
anti-aliasing can expand the (partially) painted pixels of a glyph
just one column/row in each direction, but for safety use a two-pixel
border. (Defensive programming, eek?)

Some getWidth() instead of GetWidth() etc craziness. Using
<tools/gen.hxx> types truly is programming-by-coincidence as Thorsten
says.

In a dbgutil build, setting the environment variable
VCL_GLYPH_CACHING_HACK_NO_ANTIALIAS causes the code to turn off
anti-aliasing for the fonts used. I used this to verify that it indeed
was anti-aliasing that made the ABC widths inconsistent with
reality. Not sure if it makes sense to keep this code in?

Anyway, now I don't see any leaked pixels in "i" glyphs any more,
touch wood.

Change-Id: If527343ff1dcdb1fa208cd5e7fa4d08f812d0d7b

Change-Id: Iad48cf4949cb4a398a8abee32febaf8e152dade5

Change-Id: I887c358161f7ac4032b9ad9166ff16aa0b19eaa1

Change-Id: Ibf5095fea20314180a4e002295c89f570d66d45f

Change-Id: I1bfb99b1715a907a03af5a30df6c7a41f91fd2fb

Change-Id: I7033e1e60f67e93a31d19ea08513982643dd61ae

Change-Id: I4fdc77c6fde93d9d1ee814f7614a1c4c81e18247

Change-Id: I2120ed72c281d2078e387f7f3ae91004ad95822c
Reviewed-on: https://gerrit.libreoffice.org/17855Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Katarina Behrens <Katarina.Behrens@cib.de>

Change-Id: Ia7de1cebf6009e770ca1b96bab6d5e121573ccc1

and thus fix xlsx-specific issue that 1st sheet can't be hidden.
Also kill some UNO in the process.

I'm not sure if guarding against all sheets being hidden (by having
at least active sheet visible) is absolutely necessary, but better
be safe than sorry.

Change-Id: I4ad21d223b2effe427ab1d5411c035886f6cc71c

Change-Id: I1b74fdfaa09c4d0d6c296253958e83e78b546a9a

Change-Id: I2665a12251921523045f4071df88ca69ecd5a5c0