Commit 74c5ed19 (DOCX import fix for
table with auto size, 2013-06-26) correctly recognized that in case the
width type is auto, that doesn't always mean text::SizeType::VARIABLE.

However, when the size is fixed, then we should simply not do anything,
and that'll lead to the right behavior (by setting the column separators
on each row), don't try to be smart and try to set
TablePropertyMap::TABLE_WIDTH here.

Change-Id: I997b88e5fa34bbabe7c6940879c81a1d62d69043

Change-Id: I8b246e198f3b19e65feffb196afdecb1755a0581

Change-Id: I41e9961ae797ac99fdfb1480e1a58dbe92178bb8

Change-Id: Ibf6093946ef1dec1a2ba202917da9e4562c10d3e

Change-Id: Ie413372ab1cfc7e38570fdf65c6daca8c2cc426b

and

coverity#706196 Use of untrusted string value
coverity#1244947 Use of untrusted string value

Change-Id: I5083aba2eff9e852a24513db431585922302b279

Change-Id: I03b8404f90b6a05189591d8e3423f32810057a47

and

coverity#1242727 Untrusted value as argument

Change-Id: Ibb212c39f43bcd3f0e0ddf973d1512ed0d7c2fc6

Change-Id: Ic79bd1931ee291746b6dae138b3181d4baddbe3e

Change-Id: Id5f2c8d199ffae4f23934ceb92184562d72c0b90

Change-Id: I2f104c64601b22ce3ef078295c7da3cb21a133f9

In practice, currently possible values are ASCII, but then this string
becomes part of URLs, which are in general no longer ASCII, and are
OUStrings. Instead of trying to guess the encoding of the string we get,
require callers to create an OUString right away.

A follow-up commit could adapt SfxTabDialog ctor,
SwFrmPage::SetFrmType() and SwFrmAddPage::SetFrmType() accordingly to
avoid the new introduced OUStringToOString() calls.

Change-Id: I087ed2bb341f5aca59e15e2ef4102556ca803363

Change-Id: Ibdee512a330d4520a32a56d2f1703dc2eab4981f

Change-Id: I5a01162d2925eede97f1cdc24aa876179b8b43b4

Change-Id: I771004b7ccab3344a67e827e45bc34c22ffa5f77

Change-Id: I848505b1d4ff03779b89a08d4aeefd6ea0ff205b

Change-Id: I532a1b059239b51009ea7025fb348dcd865748ff

Change-Id: I6f9049f6b5261f6099e97c7f10d6ab6ea7eaab9b

Change-Id: Iddf7cad771d271e848ba3abc1c144b9c313cdb99

Change-Id: I7508ee67a10b43686600b41dd58c1a8a5aa90c51

Change-Id: I0082d75aa2c00daa35d8d72e44fbb6da161f9774

Change-Id: I6a166a1691e39e21a4d765ca7dd0a7fcfba8126b

It is sal_Int32 that we want.

Change-Id: Idbe34ff9c0f39ad73ed7df9185512921294b3b4e

Change-Id: I96d5dc1267af714e78e431581592e75f0bff73f4

crash started after...

commit 0218b0e2
Date:   Mon Jul 15 19:45:44 2013 +0300
    fdo#65457 -  Provide visual clues in presenter view.

Change-Id: I19d84800bd5924f2dcc9e5debcf18ef95577105c

Change-Id: I8710b698904d5c89644633bb53b78a95dcef7d7b

Change-Id: Ie88b0b23b7b6f688f920f5aadcf711ba15602686

I guess it would be futile to expect some warning at run-time about an
unrecognized attribute.

Change-Id: I04ccaa6df8ec932f747384486174c1fd23eb110a

Doing .ui "manually" is not *that* verbose;)

Change-Id: Ide50258174e86cc94975a33c5c0e5c663ae8d77c

Change-Id: I5a6ef8f5e428ec4e62b3fdac8fe3e63f0ae58f1b

Now the new options show up in the "Detailed Calculation Settings" dialog and
are saved and restored from the per-user configuration.

The code that manipulates the "Detailed Calculation Settings" dialog is quite
ugly with all its manual hiding and showing of widgets depending on which
detail it is that is being edited. This also means that the dialog cannot be
designed using Glade. But no time now to re-work this.

Change-Id: I03a3a51d902084e73aab5a787b588d22ea7578f2

Change-Id: I316ebdb017d512e72d0ad15a847802bca0e15814

In CppunitTest_sc_opencl_test we want to explicitly disable subsetting and use
OpenCL maximally, to match how it used to work.

Change-Id: Ie900adb5fa58b7cd1111169e44efd70d8cac5256

Change-Id: Ie180d47558bdb9496ef55e39652f33ef52d1addb

Change-Id: I6c6fcc492f338cd8994bbc781bbf71abb6bf5057

Change-Id: I37d54e39186fca2653717bb364072a2b283bcfb9

Change-Id: I9ecea99a921a9230fa80f813627db6cdf7ed5875

Sure, this is probably "defensive coding" and the root cause is my other
changes...

Change-Id: Ia888921fddc48dc022a3205c7e0abc7e2160cf5c

Add a boolean whether to use OpenCL for just a subset of functions, and a
numberical minimum length of a cell group for OpenCL to be used. No
functionality or GUI for this yet implemented, just the setting fields.

Make whether to use OpenCL default to "on". Sure, this breaks stuff right and
left for now. Fixes and workarounds later.

Change-Id: I09b7aff9c7d1845df2bf01f09616e646373f030c

When the accessibility roles for DOCUMENT_SPREADSHEET etc. was introduced
the following places in Windows specific files where not updated to take
these new roles into account. This patch should hopefully fix that. As a
side effect the initial code for tracking cell movement in Calc works again.
Well at least as well as it did before the change, there are still some
quirks left to fix.

Change-Id: If3cacdc27a73c4cee85b1450c406d490bd741456
Reviewed-on: https://gerrit.libreoffice.org/12261Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>