This is similar to SwViewShell::isTiledRendering, but while SwViewShell
describes a state of the application, this one describes a state of the
output device. The output device may be created by LOK client code,
while the view shell may not be accessible from lower layers of the
stack, so we need both.

Change-Id: I82f7755eb73603bd79283272fba4970dccae8784

Change-Id: Ic68145a0f67ce9558570ab95b8057271c22481a3

With ACTION_MULTIPLE more characters have been entered at the same
time. In this case we send more key press events to LO for now.
This is generally useful for IME input but Android also sends this
if non-ASCII key has been hit - even when the key is only one
character.

Change-Id: Iaf48ed4e40b8e4413ed5735add34870ec263b61d

Change-Id: Ib231edd7b659ca3d0360bb3ac3021ead652f5458

Change-Id: I5cf4d5db42f32b7c073e5899a6c90a3354dcb3c5

Change-Id: Iba56deccf3c342ac82ca6cf78e09caf323f4a14d

Change-Id: I289cca3835350a00dbefa4cd8b35ae065477a683

Change-Id: I676475c028d446ff5f31a11990a09da54245f9ef

Change-Id: Ie64df7832daa002daa912c26b3c6f9f2497e0348

Change-Id: Ie8178e34698ba686e899ddd8e4f8775081fc9d83

Change-Id: Idd087e41c54bf1cf3d0f5d92f9a8058d982c0a80

Change-Id: I1c0657e512e6d3bf7a4742a356f201c993aef658

Currently the tile reevaluation was done in UI thread which could
cause UI stutters as reevaluation is not a simple task. The
result was also a lot of tile rendering requests to LOKitThread.
This changes turns this around and the tile reevaluation is done
in LOKitThread instead. Now the UI thread just sends a LOEvent
when the reevaluation should be done. This should also reduce
the amount of messages that are queued in LOKitThread, however
an execution time should increase.

Change-Id: I01ce911226a71607c06da6100de323ca555db474

Change-Id: I50bee82140e444d918ca759816edf6992a47644b

Change-Id: I976384ac5515295a56bc1339791ab63a62dc4bea

Change-Id: I0e0a072cbe31c85f5f2f9459ad724edcd8d5986a

Change-Id: Ie4de7682d4f5b7e677e23fa8aae3548040bffdc7

Change-Id: Idbc18a721c482fccd80d9c7da00f5f5dca1a864c

PriorityBlockingQueue doesn't preserve order within equal elements.
This means elements with same priority will be returned in
arbitrary order, which we don't want to have - for example we want
tiles to render in the same order they were added to the queue.
Also there is no measurable or felt benefit that priority bring so
lets just drop PriorityBlockingQueue for LinkedBlockingQueue.

Change-Id: I6ffe0bf896f0e18e8b5ffc75a4001d8f40515a56

With this, typing into an empty document + pressing Esc makes those
typed characters visible.

Change-Id: I57d05f40d1bb6afa2b8c68ce1d10906203aa4bc8

Change-Id: I070e5ccac61061730f5d0fecfc197d9fb88dca51

There were already 5 versions of this in sw, 4 for SwRect, one for
Rectangle.

Change-Id: Icf8c78f9973d940a4d180b6f52dda9ea1be86c14

Change-Id: I2964c030f420638672da5390e11179aee28043e5

editeng is not happy with non-zero char code for css::awt::Key::ESCAPE.

Change-Id: If26923df7defb8a47766e9109835a8569067e578

Change-Id: I4ba05594215564ee06c0bf9b8dff47f46e6bf451

Change-Id: I97bcc19571858fd3a43f7d5a9290a5dace7d97dc

CopyOnWriteList is a good thread safe container to store tiles,
however any change to the list makes a internal copy of the
underlaying array which contains the changes. The effect of this
is that this changes aren't immediately shown or only partially
in the other (UI) thread. So they are sometimes partially drawn or
drawn with a delay. This replaces the CopyOnWriteList with a
simple thread unsafe ArrayList and introduces Read/Write locking
to all ArrayList operations. Read operations don't lock, only
a write operation locks access.

Change-Id: I5783c6cde96360a6fd47faa801eec35e4debb792

Change-Id: I8395bae805a89558dd6c7517ea6c6a20b943ebff

SdDrawDocument inherits from SdrModel which already has an XML dumper,
so just add an sd method that can create the XML writer and then we get
the rest for free.

Change-Id: Iac9bfb779e111f9887f171db6f5bd5151dd7e447

Change-Id: I75f32f2a99430ff65345e203ac49189fec011e2e

Change-Id: Id23c330953efeb65960878413dd9dd0ad00eef40

Change-Id: Ibf2d491ad8867facab6181bec3d26d99a3ffbcf8

Change-Id: I2ea316c9f63343290da59df7f07433e38db974c3

Fix "invalidate() is only valid inside a transaction" exception.

Change-Id: I550811a0324bece298ac1a583e4198ae280586f6

Change-Id: I15b65f6eda04fce83831d8bee03b3840a1c15095

Change-Id: I26f1819c801bb1930975b0be3f036748f843e4a4

Change-Id: I3a5a24eea62efdda435c5854c164216c91c4ab44

Change-Id: I46809f24337e56b47a379eb4c482251b97337fd9

Change-Id: Ib034244b39b185877be5791c2a86018d1b57f7e3

Change-Id: Idc006b63157daea880ba1eeac3832617a0992d48