Change-Id: Iaf6678660f3d6b9c8a7ef018013311f8af553dc2

Change-Id: Ib6383220c3cdd6fef55dee82fcfdc3472da45163

Change-Id: Idc0830c4b893f55f56e0d322e87b4eff4a60d995

iLastWin will get a valid value if !bEmpty

Change-Id: I8f598b7a9d5e8317fca0ef0fcc3313bc0691f0da

To be consequent, because Point and Size use long.

Change-Id: I776a1839ee5d2cbdbcedad2b2922cb33b94c7b37

Now if we make e.g. the stack window floating, then the watch window
will occupy the whole width of the line (and vice versa, also for the
Dialog Editor with object catalog and property browser). If we put it
back again, than we get back the previous state of the strip.

Change-Id: I634614ff2e9d5f790ad759656a79a38d49c4afc4

It appears that Color.TRANSPARENT turns into black on Android < 4.

Change-Id: I40312062726696777e218afc382d55b48ac6d42b

Lots of raw pointers have been converted to boost::scoped_ptr to reduce
the number of 'delete's and the possibility of memory leaks.
Some pointers have been converted to references, to reduce the needless
checking for nullptrs, and so simplifying the code.
Also some #define-s have been converted to C++ constants or enumerations.

Change-Id: Ifbeb78f744bac7a96c8a446ff4db90dedf85fe26

This fixes the crash of 'Basic IDE: Docking property browser under
object catalog' commit. The aPropertyBrowser data member was replaced by
a new-allocated pointer. We need this because toolkit releases it by
delete.
When the property browser is closed in the floating state, it tells
DialogWindowLayout to null the pointer. If the user clicks the 'property
browser' button on the toolbar, it is created again.

Change-Id: Ie842a72fe37dfdd2ed5921ffa2f1f41d3f2c51c6
Reviewed-on: https://gerrit.libreoffice.org/568Tested-by: Noel Power <noel.power@suse.com>
Reviewed-by: Noel Power <noel.power@suse.com>

Now the property browser can be docked in the same way as all other
dialogs in the Basic IDE and the Dialog Editor.
The property browser (PropBrw, for which PropertyBrowser would be a
better and easier-to-remember name IMO) is derived from
basctl::DockingWindow instead of SfxDockingWindow. PropBrwMgr was
removed (it seemed to be only a wrapper), and PropBrw is now a data
member of DialogWindowLayout (aPropertyBrowser).

Change-Id: I06737a5cbc985888432630714cb919d1bbbcbb49
Reviewed-on: https://gerrit.libreoffice.org/518Reviewed-by: Noel Power <noel.power@suse.com>
Tested-by: Noel Power <noel.power@suse.com>

Change-Id: Id2e309ee5b8f6feff845dba28e7474e2246865f5

Change-Id: I8d9aad9ac648aefdd1f31e09fe2ea84a698c0013

This patch fixes an error introduced in c75af857,
with OUString::startsWith() introduced by Lubos Lunak in 095ffaf5
Thanks to Lubos and Kendy.

Change-Id: Idcfb9ef59cfdf4c7b08193f5c137b985fa8b9965
Reviewed-on: https://gerrit.libreoffice.org/573Reviewed-by: Jan Holesovsky <kendy@suse.cz>
Tested-by: Jan Holesovsky <kendy@suse.cz>

Change-Id: I5e809f38a500ab818e9acef80b419dfece7a29fa

Change-Id: Ibd18d9dfbd18176bc13b5c2a79a6535604e95b73

Example spreadsheet: http://www.gummy-stuff.org/Excel/Yahoo.xls

Change-Id: Icd16ed4fb05986bc199ac3f913cee656c7a434ff

Change-Id: I8903dd6aff6cdd6a4b24e3030309780975ea9318

Change-Id: I2470e0d1ace4139a735e9de32c124bc054b8ff76

This removes some possible code paths that IMHO only added complexity
and shaves some time off each presentation start (200--500 ms on this
machine) by avoiding one call of GLInitSlides, which creates the
textures.

Change-Id: I0f66d138f14c86c87d6046276adc36072227c859

Change-Id: I93b7c3796acf2da0ba28d3ae61aab4e15681683f

Change-Id: Ia4a3a2aede8240d98423dbf78da15b95e19bfa5b

Change-Id: I0876e253b69fa4ec8262946339bb643aa43f3bad

Change-Id: I481e1acfee06e56932bf7ba7bbe7f89f35ff0435

Change-Id: Ib5976cd3e0c6e3b90fc62fe8336317f259dd544b

Change-Id: I50918435903a053ce99487c6ad48d45552358cd2

Change-Id: Id3c206219385d6ab4673d1c8f6236a6cb665512a

Change-Id: I6736d1295a662527e2bfd12cfbebc0ef4634b397

Change-Id: I08a58468a3ce75038b65a8d9641cc2138541a7f5

Change-Id: Ie8a128db35bebcdcee5eda984a7875339418d9bb

Change-Id: I0ca050a8d0e9f92308ecf0525ee7f0c32ddd0492

c589da46 d71b97c1 b4aa7d03 414848b2 561c30b3

Change-Id: I364af06741f0400e25901bb7a4faccf674f991b7

Change-Id: I80abc4412055299603269a8385166718b8911428

So the build will not break on translations errors in help.
English segment will be used, when the localized segment
has fatal error in it, e.g. a tag error that results in
invalid xml.

Change-Id: I8a74649d1f00f6379a7244f2582d27b8a437cd2f

PrintFontManager is accessed from sw since
11f7d6ac

Change-Id: Ia8124acfa15386b126af2133830e1803bcf1a70f

Change-Id: I44e6b162a190939bfa17e04f551309d6249c48df

The typedef for DBusGObjectPath is only present in newer versions of dbus-glib.
It is equivalent to a gchar.

Change-Id: I1660234760fde7c7d88721f39d86a820c89040cc

Change-Id: I1e48b478a42d2b554e165922b08354b971f971b9

Change-Id: I81d7369218ae8e361f15d811952a8f690a32df96

Change-Id: I228ca76c34e3e18ea4d4f2197db20222319ebbd0

Due to the setup of gb_DEBUGLEVEL in gbuild.mk, gb_SYMBOL was always
enabled when --enable-dbgutil is set, with no way to override it.
Fix that by turning configure's ENABLE_SYMBOLS into a tri-state, where
the new "FALSE" value, set by an explicit --disable-symbols, overrides
any implicit way of enabling symbols.
But by default an --enable-dbgutil still enables gb_SYMBOL.

Change-Id: I94c609863980ed1ab9c73d7a4861c394442b531d