Change-Id: I1582443cf6799dd73a3909660d524eaacbc2d909
Reviewed-on: https://gerrit.libreoffice.org/18237Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: Idf1e4bd06c2c6d2371c634e68baf4fd0a7763cb1
Reviewed-on: https://gerrit.libreoffice.org/18233Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: Ibf32ef644222a59c5fe6a9736ff64739ab24b74f
(cherry picked from commit c874bf3f)
Reviewed-on: https://gerrit.libreoffice.org/18225Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

Can now be turned off with a SAL_DISABLE_GLYPH_CACHING environment variable.

Change-Id: I7ac14d72dc0f85c0682d92492eb96bec1d207609
(cherry picked from commit 9a68eb9c)
Reviewed-on: https://gerrit.libreoffice.org/18230Reviewed-by: Tor Lillqvist <tml@collabora.com>
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: I65ed5979d35d8739367294a71620782b832cfd71
(cherry picked from commit a8fe085f)
Reviewed-on: https://gerrit.libreoffice.org/18160Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: I6b9537cf94ac1c5d996ba64ddf878745dadde254
(cherry picked from commit 452cd9e7)
Reviewed-on: https://gerrit.libreoffice.org/18128Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>

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

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

This reverts commit 6fd71992. Kendy says the
original problem can't be reproduced anymore, and most unexpected flickering
goes away with this for my nvidia card.

Also, it's a good idea in general to keep PFD_DOUBLEBUFFER and
WGL_DOUBLE_BUFFER_ARB in sync, which is now the case.

Change-Id: I7a809d1c85be4206c01720d5de9b0a5617a59c87
(cherry picked from commit dbf5882a)
Reviewed-on: https://gerrit.libreoffice.org/18223Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Regression from http://cgit.freedesktop.org/libreoffice/core/commit/?id=5d8ecad569fd7a254902da154ed8057ec61f3a83
Thank you Matthew Francis for having found the root cause!

Change-Id: I4128368a5f5df6a9fc5f7668fb1f8f330b5795b9
Reviewed-on: https://gerrit.libreoffice.org/18210Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>
(cherry picked from commit ed33646c)
Reviewed-on: https://gerrit.libreoffice.org/18224Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Should do similarly for vertical text, too.

Change-Id: I51f5ee3ba1686f151b04f98c43388e0bdfac97fb
(cherry picked from commit 860d6948)
Reviewed-on: https://gerrit.libreoffice.org/18181Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

Change-Id: I81aec0e6f8db57905826c54c3442528be6068700
Reviewed-on: https://gerrit.libreoffice.org/18184Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jan Holesovsky <kendy@collabora.com>

Treat an array of null string pointers as no strings for OpenCL. For
some reason, at least in the case of the "Test OpenCL" thing, we got
an mpStringArray that is non-null but where all the elements
(rtl_uString pointers) in it are null. Treat that case as if the
mpStringArray was null.

This makes the tests "Test OpenCL" actually use OpenCL. Maybe it has other
useful effects, too. (But for normal spreadsheet use, the mpStringArray that
gets handled here *is* null when all the cells used by a formula group are
numbers. At least it seemed so in a simple test.)

Add a few more useful (?) SAL_INFO calls.

Some cosmetic changes to make the code look saner.

Return correct value from the OpenCL VLOOKUP implementation. Also,
when the lookup fails, produce the expected N/A error code instead of
a bare NaN.

Don't claim we support strings arguments in the OpenCL VLOOKUP.  The
string support certainly isn't complete or correct anyway. Partially
revert c3383aaf.

Add VLOOKUP to the set of opcodes that we trust the OpenCL
implementation for.

(cherry picked from commit 7e91726f)
(cherry picked from commit d4310b6c)
(cherry picked from commit 32b35d9d)
(cherry picked from commit 41a60940)
(cherry picked from commit 16226445)
(cherry picked from commit 7bb7539c)

Change-Id: I5402732c9ddcac1efcc25960a5c46175d7a90b4d
Reviewed-on: https://gerrit.libreoffice.org/18022Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

Change-Id: I117fd5f5fd12fd6534b9d10532a39807ad82ce71
Reviewed-on: https://gerrit.libreoffice.org/18069Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Reviewed-on: https://gerrit.libreoffice.org/18220Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

At least with my AMD card, in case of SAL_FORCEGL=1 the startup crashes
quite early. DrMemory says:

~~Dr.M~~ Error #1: UNADDRESSABLE ACCESS: writing 0x00001414-0x00001415 1 byte(s)
~~Dr.M~~ # 0 atioglxx.dll!DrvPresentBuffers                          +0xd6ea6  (0x09a248f6 <atioglxx.dll+0x1248f6>)
~~Dr.M~~ # 1 atioglxx.dll!DrvPresentBuffers                          +0x3c069c (0x09d0e0ed <atioglxx.dll+0x40e0ed>)
~~Dr.M~~ # 2 vcllo.dll!OpenGLContext::InitGLEW                        [c:\lo\master\vcl\source\opengl\openglcontext.cxx:949]
~~Dr.M~~ # 3 vcllo.dll!OpenGLContext::ImplInit                        [c:\lo\master\vcl\source\opengl\openglcontext.cxx:866]
~~Dr.M~~ # 4 vcllo.dll!OpenGLContext::init                            [c:\lo\master\vcl\source\opengl\openglcontext.cxx:786]
~~Dr.M~~ # 5 vcllo.dll!WinOpenGLSalGraphicsImpl::CreateWinContext     [c:\lo\master\vcl\opengl\win\gdiimpl.cxx:36]

Turns out that in order to enable the GL_DEBUG_OUTPUT_SYNCHRONOUS_ARB
extension, the GL context must be created with WGL_CONTEXT_DEBUG_BIT_ARB
set. It seems that other drivers did not enforce this so far, but in
this case the driver just crashes without this.

Fix the problem by splitting out the debug setup part of InitGLEW() into
a new InitGLEWDebugging(), and at least on Windows call it only after
wglCreateContextAttribsARB() and wglMakeCurrent(). Additionally make
sure that in the debug case the necessary flag is passed to
wglCreateContextAttribsARB().

Conflicts:
	vcl/source/opengl/OpenGLContext.cxx

Change-Id: I6b77e0c06fd85fdae0386a0801f1de1838524586
Reviewed-on: https://gerrit.libreoffice.org/17750Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
Reviewed-on: https://gerrit.libreoffice.org/18219Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

For each iteration of the (gtk) main loop we are dropping the yield
mutext which results in calling OpenGLContext::clearCurrent. That method
calls OpenGLContext::ReleaseFramebuffers which would call in the end
glBindFramebuffer for each framebuffer related to that context.

This would easily grow into the thousand OpenGL calls without doing any
work.

Change-Id: I209cc534fe58a5e11ef7df7f850a787916b8bd43
Reviewed-on: https://gerrit.libreoffice.org/16241Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Reviewed-on: https://gerrit.libreoffice.org/18218Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

SubdivideBezier creates polygons which are more exact for drawing
in opengl when drawing hairline PolyLines - so let's use that with
AA line drawing.

(cherry picked from commit b3de73f3)

Change-Id: I490fd0f19361b5fc9e1f4e03851c1ae1a1f75f71
Signed-off-by: Michael Meeks <michael.meeks@collabora.com>

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

Change-Id: If0dc78a2d6e3c9fccf37504902abab07bfea8200

Follow-up to 34700400; this fixes sw_ww8export
unit test on Windows.

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

Many places were already adapted for the tiled rendering, and the conditions
checking for the VisArea() were changed so that the checks are ignored when
tiled rendering is active.

Unfortunately there are still some places left, and they are causing that
various areas are invalidated only partially.  Let's sort it out for good, and
report the entire document as the VisArea() when the tiled rendering is
active, and if there are performance problems, let's profile that & act
accordingly.

Change-Id: I53f18915ed0aec898704dd1350a9534cfc3f001b

In that case we get a NULL pSlot.

Change-Id: I38783ed198b1ab9860398f59ef872a295cbae6f8

A better solution is needed, outlined in tdf#94233.

Change-Id: Ie2a58c9c5f5c46566da105ef84d736d7290f4634

In the tiled rendering case, the desktop is headless, so the toolbar
is not created.  The toolbar usually initializes all UNO url commands
for each tool item attached.

This causes that SfxControllerItem that monitor a state, it is not
intercepted by InterceptLOKStateChangeEvent so no callback status changes.

Change-Id: I5937cda66ef24d31dd92a1edd8c1440081c4b1a4

Change-Id: I92fd5022a4a5736a6323732141e9ea7bafec2a44

So far it just selects 'Approve' for any interaction that is done through
that, later we want to route the information via callbacks to the caller.

Change-Id: I7ae3e2dcc04877b8b0197b0396299126e1217a2a

When there was no modification to the document, and .uno:DefaultBullet was
sent, we have got an invalidtion of the entire document.

It seems that Invalidate() was not supposed to be called in the Validate()
call, and instead, we should rely on what the Validate() invalidates :-)

Change-Id: Ia65df90e4ff34078b59c1b2eb1ce1faac790b40d

Returns a json mapping of the available fonts to their possible font
sizes

Change-Id: I80c0bdd79e3ef2d814f64b8d38143d6c2b9ca720

This method returns a JSON mapping of the posible values for the given
command (e.g. .uno:StyleApply, etc).

returns:
{commandName: "cmdName", commandValues: {json_of_cmd_values}}
I've fixed the unit test this time

Change-Id: I30b0fba8ba1db33dd79f4b46026d293b9ea72402

We needed a better way to test LOK methods that are not app specific,
but are defined in /desktop/source/lib/init.cxx. So the decalaration
needs to be visible.

I also moved the `getStyles` test in the new test file

Change-Id: I98d97dc17a66e72732ca7bd848c131610790f48e

Change-Id: I866a44fcb71044d27a9bf06e2f55ca2e4135c23b

This method returns a JSON mapping of style families to a list of styles
from the corresponding family.
Will be used to know and apply styles in tiledrendering.

Change-Id: I0aa395c40b9573920ade44255f97c077475ae5f1

1. For tiled rendering, don't invalidate the whole page when hiding it
2. Don't invalidate when showing a page because we've just hidden the
previous one
3. No need for invalidation when setting visible layers

Change-Id: I858401b22c95093c58ec00896fe92b766fddb6de
Reviewed-on: https://gerrit.libreoffice.org/17452Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jan Holesovsky <kendy@collabora.com>

It is necessary the thread name for debugging LOKit threads.

Change-Id: I713595eb1319234ff90a6eddebcac5ebad912b04

Change-Id: I3965966f0d3fe65389e8834d67452ac56f9df2d6

Change-Id: I80cd2975f17bb7fa57fa669873ef1dd8f3595a11

Change-Id: I2b86f79e83b3facf3e54009d3e7c9b7667b5b377

Change-Id: I4f33679332998f87b7bf1ad7c32aea64897dcaa6
(cherry picked from commit 0590fe94)

Change-Id: Ifdba1eaf4cec448fe3284015c36ea7fd1b3440b0