Change-Id: I64f76d22018fcd8af2991933ba5ab2069f84181f

LOKit supports searching, but this was not implemented yet in the
Android GUI. This adds a bottom search toolbar where you can type
a search string + up/down search handles to search for the string
from the current cursor position.

Change-Id: Ia7461d2c6399c23201d2ea81f0b44c38533939a1

The bottom formatting toolbar now shows the formatting options
previously located in the main toolbar as a menu entry (bold,
italic, ...). In addition alignment options and selection of fonts
and sizes have been added.

Bottom formatting toolbar is not shown by default - it enables when
hitting the icon in main toolbar. Also soft keyboard and formatting
toolbar should not be shown at the same time.

Change-Id: I5f6cf8a9fcbdb4d154ae7504a65f9a226c99d694

Change-Id: I5b4dd8b8c407640cfcd9f366cecfaf6deb0cb3be

Change-Id: I7d3742af0c11a996701f7d263fc04a387edb0d00

This has now been merged as:
LOK: setClientZoom() - sets the client zoom level
96cd2abd

Change-Id: I519a752dd9f18bb719a43f75f1ad3105f58418d9

Change-Id: Ia802c19f5bfd2fe2e9909e3c611047c529a64200

Change-Id: Ia19d14def4b78b85ec9ddabb706416a971b670cb

Change-Id: I0d070dee9e940b93b294c6b2de180005a5c2248e

Change-Id: Ife26f55c28c4631aec4ba4105225bfca72da8bff

Change-Id: Idb0eacc8c14b2c56e8255c47c8330e5e6572d5de

Change-Id: Iede68e39a449ad0ea4a07d0a349c70c523ad6633

Change-Id: Ief31d8153fdbf91cdd29df5ac7801bd88a98542e

... and mpErrorBmp to actual members (not just in name only).

Change-Id: Id02553451f1990dbc111e9c842247764bf7554bc

... but there's no point in them being static either.

Change-Id: I49931289560da9de7a2e79577e525872d316cc4e

... and associated copypasta

Change-Id: I59a34da48727c84953ed460c11718d261fc3c5a1

Change-Id: I0cb6112b0353a5fd0b4dd571d65f2d656e39ba74

Change-Id: I6092d64f0e64d295253505b27c9aee7874d9ecce

Change-Id: I6f4d0bb57c5d82984ff29b621dc4570f453be31d

Change-Id: I6520e47198a3da4e72fc77c6a6955afac410c7fa

<erAck> mst__: I see no immediately compelling reason why that shouldn't
be a member variable

Change-Id: I307259337cb068c5c7e397a1f57cf8e7c92b0e12

Change-Id: I6dc352bf0bcfef18b39926986929d0ba96d2f3cc

Change-Id: I98246395bb0de7444864ce35d1cbdd4711b5bfeb

Change-Id: I3d892ba544e1c3e569e3c1968e034836dde5b555

Change-Id: I69bb8ab014864ad77448785dfcd291d7c51a0cef

Change-Id: I3dfa3f5933010adb4c9277aac441a8c8a7c9c4b6

Change-Id: Icb37c70535fec579effddf39f2e60e4418c9d98e

Change-Id: I3745d31135062778ce5ec618f1d491fb21a540f6

Change-Id: Ic162dd2d9a97e7d311921fad7d4d2bdf4b81293b

Change-Id: I4491ed75bfe588b5c4e307d17319e1f0feda1678

Change-Id: Iaf779157b97e4d3a3a449cc7f17e4d5c533955f0

Change-Id: I71e0de9e13718c1a6cd11339aba740effa2e0476

Change-Id: Ib07e85bd1a157b6fa78f07a17f8cf5033b01bddf

Change-Id: I2f79e52da2aa0ad3a37aac07a36dbe14dfe401a9

Change-Id: I3ef314594b64a54aca389816fd9bf5ba0721b397

Change-Id: Iafd6e5f899835303e421be923f70d1e3f42bf65e

The basegfx Triangulator is used in slideshow with canvas to triangulate
the mask geometres. This uses tools::isPointInTriangle which uses
basegfx::tools::arePointsOnSameSideOfLine. This uses the cross product
to solve and for tests against zero the fTools::equalZero call. The
triangulator then uses the more precise rtl::math::approxEqual to test
if one of the points of the triangle is equal to the test point.
In rare cases this can lead to a position where a point is seen as inside
the triangle wrongly because it is not detected as equal to one of the
triangle points. To solve, use increased accuracy.

Change-Id: I73e12b711f14d4c48e829d5db1cadefa0917c19b
Reviewed-on: https://gerrit.libreoffice.org/19925Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>

after my commit 2aacf6c2
"sc: boost::ptr_vector->std::vector"

Change-Id: I7195b91a61405f16ddcc698ce1e8205e6d20c39e

Change-Id: Ie89b64c4399cd0092eee579660c9fe85f8ca8e73

This is primarily for tiled editing that doesn't know about multiple
cursors, so if both the postit cursor and the main cursor is shown for a
short period of time, then the main one is hidden, then gtktiledviewer
still shows the main one.

OTOH if we can avoid showing the cursor in general just to hide it a bit
later in general, let's not do that.

With this, the "cursor is shown at the comment anchor, not inside the
anchor when clicking on the postit" bug disappears.

Change-Id: I2383292c5f84604dc8b126510b0797b8426920ae