Change-Id: I62e0ec63ff09c200e0b621c8b042a976e8ce630e

Change-Id: Id6ceb78985e9578ea952a37988a7f7655e2f1a12

Change-Id: I83d411adf8ef882618bd48ab73602f7cf1531078

Change-Id: Ia4cd4faaffaf42555b16ada5e259e85ddb496236

Change-Id: I8e40cf9166aa65c81cb6b4ed17506ec5b9d725e3

Change-Id: I946e1970647d8005f54ac0362f5c2b04f867b22f

Change-Id: Ib0f01af2c7a7186d138369c177a563b322a87214

Change-Id: If39ad8e936b3a46de00770993a4a7c3676c676d2

Change-Id: Ie7fa4e1cee488bc84e2ded40725cb9044b99d3cf

Change-Id: Ifb4f8c039829ef326d81dd7a0e36b3b527451c21

It seems to be fairly CPU intensive to calculate the MD5 digest of
shader program source code. But we don't need to use that to look up a
corrresponding program in the run-time in-process cache anyway. The
shader names are unique, so it is enough to use that as key.

Change-Id: I8fd9f5f875be14a82cd53daf8a2ca72bfd23beb6

Change-Id: Id4548aa2e32f736f4cd332ba824137d88fe963fc

Change-Id: I24d29ffc3cfcb00e513a5267619e143b028355ce

but docshell isn't and we're using the view apparently
to get the shell we already have

Change-Id: Ibc2021245191a75f65ec655a2d1929601a2611b5

Change-Id: If070da723858b5e1221bda86e69225ee57ec9d02

Change-Id: Ie6863f446aa688bc1bb3f725ee31e9984dadc7a4

Change-Id: Iec3266746c78e58e3c3a094e6511d79dadc4e4c6

Change-Id: Ifa75a0344c444f589c165562262a8d843cd12ef7

Change-Id: I0fe9cb55de114c7e2ad45cd946e94f9c0e93b85c

Change-Id: I760bd9ad3d0da20c0ad38aace765a42983e28531

Change-Id: I2ec12da777d04855d34233d5781f2304e181bbbd

Change-Id: I1d8fe58c589b56590453b2136296ca50bfe78252

Change-Id: Ib3931639f7407f274700ab96f01a67d6f26925f4

Change-Id: I57c15ba4374b626db322f42f04adc088b8cf6ce0

This commit fixes the writer image export (jpeg, png) that didn't
work because the export pixel size was set to 0 by default. Now
the default is set to document size (which depends on system DPI).

When exporting to a PNG the background was transparent, which may
not  be desired. The background color is now by default white and
can be changed for DocumentToGraphicRenderer, but the dialog or
command line don't support such an option - for now.

Change-Id: I16ffd3cd60c47b52768f43ae4c4c170fc821033b

Change-Id: I0a1ad60cb6eea26899604641f981642943b06347
Reviewed-on: https://gerrit.libreoffice.org/19375Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

Change-Id: I4bb861649375b5c6178df6820eb2c759111340b8

My thinking was that there is a slight difference in meaning; that
assert() checks that the code (or, in this case, data) in the test
*itself* is as expected while CPPUNIT_ASSERT() checks that the
functionality *somewhere else* works as expected. But whatever.

Change-Id: I93f7f8cf2b3aac9e8fc35baf2dcbad1a4003773f

Change-Id: I13a290cba0f38c79eb2d93148b972d3d931c3862
Reviewed-on: https://gerrit.libreoffice.org/19445Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

I know the comment in debug.hxx said to use SAL_INFO, but SAL_WARN makes
much more sense.

Change-Id: I3d81f9db89ef8cebe1e4f2983941d69b4c7e6b7d

and drop the macro

Change-Id: I452ca373d0c277166e94928c1bce78bf37e39d7c

found with
   git grep -nP '(\w+)\s+=\s+\g1\(' | lots-of-hand-filtering

Change-Id: I598b0cfa6607823eaef09d95e610e05145c727f7

Change-Id: I8a153a4b3a1bdb8a298c3c76a6b51693c42a0688
Reviewed-on: https://gerrit.libreoffice.org/19444Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

Change-Id: Ifb59fc408bdbbe7edcb78f1c48dc462422f21a71

Change-Id: Ia27922e630373d0520f25d259bb06aa25407089c

Change-Id: I8182e45dedfa70b41166b1d5fe5e152ae4b8c8ff

Change-Id: I6c032633eb36402aa9050587bedf9530d7e0ba71

Change-Id: Ib47ec3687972c2941cbe64b216a0548f2f7261fd

Change-Id: Ifc1e9e64f50aa916ef0667796a54a11dec9a0ea8

Change-Id: I65f4cc10c4a3dc5ffc21b64d76dc32f1613a0062