"warning C4510: 'XMLEmbeddedObjectImportContext::{ctor}::<unnamed-tag>' :
default constructor could not be generated"
Change-Id: I3c81bf4c0fd20795e20f5c0f2e790bf4118c0e2d
The default TextHorizontalAlignment is block. Setting
paragraph alignment (on UI) works when this text
alignment property is set to block (otherwise has no effect).
In general this works on this way, but the existing
algorithm did not work in those cases when the
text was bigger than the container shape.
Change-Id: I02dba76f8e3033a465bb14dc826521966bb30987
Reviewed-on: https://gerrit.libreoffice.org/32123
Reviewed-by: Tamás Zolnai <tamas.zolnai@collabora.com>
Tested-by: Tamás Zolnai <tamas.zolnai@collabora.com>
Empty paragraphs are removed in certain cases. If the previous
paragraph was in a frame, then this one shouldn't be removed
(unless that previous paragraph was in a header/footer).
Most of this patch is renaming the function to clarify that
it refers to the latest paragraph, not the very last one.
As noted in original tdf#75573, there may be other paragraph
containers that should also ignore their framed status - so
I've tried to set this up to make it easier to add those cases
when proof documents are found.
Change-Id: Icd09793f652616622ab266942f4b81eeb39c0ccc
Reviewed-on: https://gerrit.libreoffice.org/32121
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Justin Luth <justin_luth@sil.org>
...by:
* making the OUStringLiteral ctor non-explicit (to be exploited in a follow-up
commit)
* adding (LIBO_INTERNAL_ONLY) overloads to OUString/OUStringBuffer functions
that can now take OUStringLiteral in addition to taking "real" string literals
(Keeping the number of overloads smaller by replacing the ConstCharArrayDetector
overloads with ones taking OUStringLiteral (for LIBO_INTERNAL_ONLY, at least)
and relying on the now-implicit conversion from "real" string literals to
OUStringLiteral unfortunately would not work: Both OUString and OUStringLiteral
argubably need implicit conversions from "real" string literals, so any function
overloaded for OUString and OUStringLiteral would be ambinguous when called with
a "real" string literal. And removing the OUString ctor taking a "real" string
literal and relying on an implicit conversion chain from "real" string literal
to OUStringLiteral to OUString doesn't work because it would involve two user-
provided conversions.)
Change-Id: I14433fc1605b048807f60b3a3e14f92221d3a226
Reviewed-on: https://gerrit.libreoffice.org/32097
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Tested-by: Stephan Bergmann <sbergman@redhat.com>
since m_bBorderDist is currently always true, this will not have
any real impact, but it should be ,m_bBorderDist instead of ,true.
Fixes commit 5d9d0f3c97
there is a function for that: CalcLineSpace(xx, bEvenIfNoLine)
Change-Id: I5c7f6ad02d2a4c426e2d231c13d3d38ce45b7a1b
Reviewed-on: https://gerrit.libreoffice.org/32112
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Justin Luth <justin_luth@sil.org>
This may have been the cause for some tinderboxes choking on this test
on Windows and Mac if the forecast results slightly differed due to the
initialization with random values and the calculation taking place with
a different internal floating point precision. So let's try.
Blindly throwing ROUND(...,12) at all values is wrong anyway because
that doesn't take the magnitude of the expected value into account. What
we actually want is an accuracy of 12 digits, not an accuracy of 12
decimals.
0.123456789012
1.23456789012
12.3456789012
123.456789012
...
Change-Id: If88d75277c3d17cfd72f36d0f88d093b63da8add
or footer. Some very special handling going on to paint these in
VOCOfDrawVirtObj with a GetSwDrawVirtObj().GetOffset() added;
they are falsely identified as invisible because their
sub-objects have an anchor set but it is always on the first page
so to properly check them we'd have to add the same GetOffset()
thing but checking the top-level object should be sufficient.
(regression from 689cead9e0)
Change-Id: Ida6fcd41948f46410ca02193549e426bc9dae8c5
It turns out that draw objects in header/footer often don't have
AnchoredObject::mpPageFrame set, so use FindPageFrameOfAnchor()
instead.
(regression from ae06f4be6b)
Change-Id: I6d54baa3acffa6775d5b57a1517c77a964065dd0
since...
commit 880e622d2e
Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
Date: Sun Dec 11 14:30:44 2016 +0100
refactor out lcl_GetWW8Pos
IIUC the old code only changes the X/Y if its not NO_CONV for
that direction, so lets reintroduce that and then drop the assert
Change-Id: Ia5b0e668fff83466dc2ab59aa163cb9a87984b0e
Now it broadcasts "disabled" to disable the command and
true/false to tell the status of the command which automatically
means "enabled"
Change-Id: I3314da77fb2b84d97f64b9832d65791b84fcd7df
Reviewed-on: https://gerrit.libreoffice.org/32086
Reviewed-by: pranavk <pranavk@collabora.co.uk>
Tested-by: pranavk <pranavk@collabora.co.uk>
(sal/inc/rtllifecycle.h only hits on Windows as that is the only platform that happens to
actually include it in a C compilation unit, sal/osl/w32/dllentry.c)
Change-Id: I2878b52daf713ea45eaa2968cc5d2686b86abfe6
Project: help c349db3a49bae0d8a45528b8889bd36b337117b4
Update 'Insert Names' dialog to 'Paste Names'
There is a new terminology for the same thing.
Also document a new button.
Updated the bookmarks and ahids to restore connection
between UI and help page.
Change-Id: I05eaad7546dbedcf065b9a97b830550e1ec22515
Reviewed-on: https://gerrit.libreoffice.org/32063
Reviewed-by: Olivier Hallot <olivier.hallot@edx.srv.br>
Tested-by: Olivier Hallot <olivier.hallot@edx.srv.br>
Project: help 2ecebd5cd909f68f388490f26da74e67416f274f
Restore connection between the 'Insert hyperlink' UI and help
Renaming hyperlink to link is still left to do.
Change-Id: I1d7b472cbd0511c80e25a7c433b08e5a79d5d592
Reviewed-on: https://gerrit.libreoffice.org/32062
Reviewed-by: Olivier Hallot <olivier.hallot@edx.srv.br>
Tested-by: Olivier Hallot <olivier.hallot@edx.srv.br>
Two accessible document is created when "freeze" options is
enabled. meSplitPos identifies which accessible document handle
which part of the window. We should handle events only in that
accessible document which handles the active part.
Change-Id: Ic9674344951f620546dd272beaad796de611d258
Reviewed-on: https://gerrit.libreoffice.org/32065
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Tamás Zolnai <tamas.zolnai@collabora.com>