Change-Id: If5990d41f444a2d051c9b9029d61ffd8b8cf377e

Change-Id: Ib204b6ab39872280c8889615170735ed8c1fc811

Change-Id: Icad89fe16e428a5e4d87ab4b19131bdd804528b7

Change-Id: Ib4a569fc299325982b6e0da02311acc55fe18760

Change-Id: Idc2026ff65dfaf36ea4be21ae9557cf5534e8c6b

The CoreText implementation dropped the support of DXArray
more exactly ignored the values provided in it.
And try to approximate the result by assuming that
all it does is full justification... which is not quite right

This ut the feature back, buy handing the glyph drawing
directly, rather than defering to CoreText CTLineDraw
to control the position of each Glyph

Change-Id: Ibe0cfe789d3be441c012d8ac1104d939204a591c

Change-Id: I00bf83c82814cd3d215bda361a14eb01836e2d0a

Change-Id: If0f6bd93adc5d39fd421bb482833619f85f7a461

Change-Id: I0b03973b2d09a0ce51a6ee7dcca5a310a544c3a9

most of length in vcl are calculated in 'long'
but array of X position tend to be in sal_Int32.
As a prep work to be able to support 'double'
as the base type of Device Coordinate, harmonize
the use of 'long' for non-float coordinate.

Change-Id: I7cb33301ff6a5e2c62247b36a4e07e168a58a323

Change-Id: I165e403d2834d341f7da7a280859afccb995a3bb

Change-Id: Ifba7104a13cf737200c81d1a1bd5ece9a29da60e

The eventual goal is to make vcl capable of handling a backend
that use double instead of sal_Int32 as its base type
for device coordinate.

Change-Id: I6174f1f4afe00992b95c9163bc21dd54fec98631

Change-Id: I7f500186c2ce485e7f6a857286c14d0a64354c31

Change-Id: I77348fce55db78e437431dd07879b4c26f0be893

Change-Id: Iff2bb51047d6b8698b65b83ff79a99f6f125b53c

Change-Id: Ib89daf3e608fd995845062eae2a7a33149964844

Change-Id: Ia96e85191d877ebfd7621f7aa572f29e6482716c

Change-Id: I5140f4053fbb1add4bc0b1b8cb6cd9772f3ffa28

Change-Id: I262456efc52c74aeeda1c55b24a69c4c628a26d8

Change-Id: If9b09b69ccd890e45d963422ccedb711585f6434

Change-Id: I33fec62e4bc38eeaf014eeb1210db2904af033f6

Change-Id: I2ac8f790c79c269d4c1fa650e703c3645c567ca4

Change-Id: I1477833e696edbac2dc375329e7b26a7105d1593

Change-Id: I5deac7f096866a8f149acfd0d11bbc0963238e88

Change-Id: I80055e4101873e0ddd408ac1f0ee9c75cc3bf6b3

Change-Id: Ia865b84ee2b159ff7251ab5a769a2b635dd2a1ea

Change-Id: Ic3e13e89480e3b18f84c3a8fd1a88627bd465d6a

Change-Id: I5c4f7c5713a559815bd46328907673d114fee011

Change-Id: I819de476c6a615b8cf27a6a26d41a6e9ac25ef85

This fixes a crash when this tabpage is one of the tabpages in
data series properties dialog (e.g. 3D column chart)

Change-Id: Iacbc689fb410b30515e433bcf4a96c087047ca73

Change-Id: I5c0f34f035765fcfd916b635ab18f5cb1bbcabb0

Change-Id: Ic42d506db8fe065cb8f01e17f18a1238d1eff651

Change-Id: I4232040d4c62220389ca356797d18b1c87673e64

Change-Id: Ic18e4a7ad725640ffdeb15a1982ecb9131d11697

Change-Id: Ifefa4a314fbe9380332fd02c5fc8dfbb68e09cf5

Change-Id: I0523e49e640812be435ba4c97b1881ca253eb2ab

Problem after ChartWindow was disabled and enabled
again, OpenGL content was lost.

Two things:
-After setting a new OpenGLWindow the corresponding
IRenderer must be set (x3DWindowProvider->update)
-InitOpenGL() call should not depend on DummyChart, but on
OpenGLWindow (OpenGLContext).

Change-Id: If74e1945de9973d3921ceea1ca6fef39311add7a

Change-Id: I1e23329345e00e7d8e1f269c832e84d015824c0a

Change-Id: Ie4eb55fa52ee97eb98a5269658ce5183a287618b