...and not only if the caller happens to pass in non-null ppError. Otherwise,
calling soffice with a document URL handled by the gio UCP that is not yet
gio-mounted would silently do nothing and exit with EXIT_SUCCESS, as the first
thing the type detection code does on the URL is execute "getPropertyValues" for
"IsDocument", which calls getGFileInfo with null ppError, so a void instead of a
boolean value is returned, which then derails the type detection code to
silently fail (which is another problem that needs fixing).
Change-Id: I48a84428cdee5caead02909abc2efd3ae3722052
Reported by: luo qing le
Patch by: Lei De Bin
Review by: Chen Zuo Jun
(cherry picked from commit 9b161d18404d8fac5663bc3b3a854bdd4fad3bf0)
Change-Id: I7e51d2fd6b72d08b793b857cf2a3de5989145695
Reported by: luo qing le
Patch by: Lei De Bin
Review by: Chen Zuo Jun
(cherry picked from commit 3654740a6f770631d34897aad345f006313c46b9)
Conflicts:
sw/source/filter/ww8/wrtw8esh.cxx
sw/source/filter/ww8/wrtww8.hxx
Change-Id: I1c25d17b1780adeddee46d500f2f0753944e9ffc
LimitBox set its value to -1 if the current
text is "All" but just when it loses its focus
so dispatching its value to the controller
must be after this setting.
(see limitboxcontroller.cxx)
Plus some clean up in LimitBox.cxx
Change-Id: Ic1d314a5a67c2b261b2e9c50973f51de2bfb8db8
If limit clause follow from clause directly than the statement
parser of hsqldb parses "LIMIT" token like a table alias and
that's why the next number is unexpected.
The problem was that the limit token was not added to a "keyword"
vector in which parser search while working with form clause.
If the algorithm find a keyword after table names than it
knows it is the end of the form clause. That's why it
worked with any other keywords like "ORDER_BY",
"WHERE", "GROUP BY" and so on.
Change-Id: Iacd3ea3493c85eb0f2579aaad6903537ac65d25a
to make sure the week object is released correctly.
Found by: zhangjf
Patch by: zhangjf
(cherry picked from commit 1e51e5dab1664dadb40509c4fab593fb27040efd)
Conflicts:
ucb/source/ucp/tdoc/tdoc_stgelems.cxx
Change-Id: I33d0b3b7cda2aa9a220056bf7d641b09036f89e9
* subversion/main/oox/source/drawingml/textparagraphpropertiescontext.cxx
[]WritingMode2 is used to numerous explicit writing directions, so use WritingMode2 to instead WritingMode.
Patch by: Ma Bingbing <jiazema@gmail.com>
Suggested by: Wang Zhe <kingwisemmx@gmai.com>
Found by: Wang Lifeng <phoenix.wanglf@gmail.com>
Review by: Wang Zhe <kingwisemmx@gmai.com>(cherry picked from commit 4545d293b1cf5009b075cdc82d43916909b77347)
Change-Id: Ic621ce6107bdc0b83c511f055175ae7b629f1503
Removed in 44159c6cdf , but since it's
set in CXX, this either has to pass, or it has to fail (or it shouldn't
be hardcoded the way it is).
Change-Id: If5b7b7096927f5d97c7c744cbbfea08e90f1de55
Do not confuse GCC and libstdc++ versions. Clang defines GCC
version #defines, so the old version was wrong for it. Correct __GLIBCXX__
values found from GCC/libstdc++ repository history.
Change-Id: I94f5250609f7c9a114b2d15093abc9ca4209b13f
mso-position-horizontal, mso-position-horizontal-relative,
mso-position-vertical and mso-position-vertical-relative
With this, the watermark in the bugdoc is almost in place, if you ignore
the missing rotation.
Change-Id: I8d3d834089e734654fcbbb0fb6166b4d7e01f80f
...which has become necessary since bd60d41176
"Handle oveflow in O(U)String::toInt() functions" reduces values in the range
(SAL_MAX_INT32 .. SAL_MAX_UINT32] to zero, but some calls of toInt32(16) relied
on getting a correct (unsigned) value for the whole input range ["0" ..
"FFFFFFFF"] (see libreoffice-4-1 commit 9bf6c83367cedb7be81bf67f30d2147d26c7a8c3
"Revert overflow checks in O[U]String::toInt{32,64} again").
Audited all uses of toInt32/64 with non-decimal radix. (There is still a TODO
comment in oox/source/helper/attributelist.cxx, and
stoc/source/typeconv/convert.cxx will still need some love and test code.)
Change-Id: Iadaca1c0e41dab553687d0ce41c20c10cd657a95
moving a text frame, graphic or embedded object in Writer
(cherry picked from commit ba9e13a1ebad1569cd5ccf65925a06329ba0d188)
Conflicts:
sw/source/ui/docvw/edtwin.cxx
Change-Id: I126165d6be7505223c4255262103cfb123ec3d55
due to bad quality of GraphicManager paints
(cherry picked from commit f4887567cc71dca520d57cb6ff2b40eb49142cda)
Conflicts:
drawinglayer/source/processor2d/vclhelperbitmaprender.cxx
Change-Id: Ie4b5873cdfb8bc7f1f4b288e1f983672343d8847
This reverts commit 5fe65c0c5e.
Unfortunately this causes a regression elsewhere.
This also disables the unit test for this bug - will re-enable when I find
a fix that both fixes this, and does not regress other stuff :-)
Change-Id: Iad334e3c59c928edb78f25c0f36a33a26a7e6125
