lo/core - LibreOffice 核心代码仓库

Age	Commit message (Collapse)	Author
2020-10-29	tdf#135198 fix unit test for HiDPI: pick object by index	Daniel Arato (NISZ)
	Clean-up commit c9eb53f200225f2ee6ca695e1326843a487aee51 (tdf#135198 sw editing: text box fell out of its shape). Also removed a few unnecessary lines that have been commented out. Change-Id: I6ec8535f98ed6e7743b34c9e31b0c76c0cddf301 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105006 Tested-by: László Németh <nemeth@numbertext.org> Reviewed-by: László Németh <nemeth@numbertext.org>
2020-09-11	Missing test dependencies	Stephan Bergmann
	From-scratch `make CppunitTest_sw_core_layout` had failed for me on Linux with > warn:vcl.builder:1528301:1528301:vcl/source/window/builder.cxx:467: DBG_UNHANDLED_EXCEPTION in VclBuilder > when: Unable to read .ui file exception: com.sun.star.container.NoSuchElementException message: file:///.../instdir/share/config/soffice.cfg/svt/ui/editcontrol.ui xmlreader/source/xmlreader.cxx:66 and > warn:vcl.builder:1529052:1529052:vcl/source/window/builder.cxx:467: DBG_UNHANDLED_EXCEPTION in VclBuilder > when: Unable to read .ui file exception: com.sun.star.container.NoSuchElementException message: file:///.../instdir/share/config/soffice.cfg/svx/ui/sidebarstylespanel.ui xmlreader/source/xmlreader.cxx:66 Change-Id: I021cf45a61a894a88aee64110a9b9ea8f7a20888 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102452 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-07-31	sw: introduce a Library_swqahelper	Miklos Vajna
	So it is no longer necessary to define all SwModelTestBase functions inline. Change-Id: Ia1055ff967b3614102275ec92607c85ec063fce7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/99820 Tested-by: Jenkins Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
2020-02-14	sw: fix handling of table vs fly overlaps in the AddVerticalFlyOffsets case	Miklos Vajna
	When a table overlaps with a fly frame, Writer creates a fly portion inside the relevant cell frame (increasing its height), and Word shifts the table down. Both are valid approaches, but the rendering result is different in case the table has a border. So keep the default unchanged, but in case the AddVerticalFlyOffsets compat flag (set by the Word importers) is set, avoid the overlap the Word way. Note that the table frame uses the full width (available in the body) even for e.g. 50% width tables, so check for the overlap using the print area, which does not always overlap. Finally, don't always require a valid frame area definition from the fly frame: - the mentioned i#46807 bugdoc currently doesn't need that check - the fly frame area definition becomes valid only after already positioning the table, leading to an overlap Keep that check for the non-compat case, though. Change-Id: I9202050befebf2efdbb5395ded6fcb52b378d8e7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/88724 Reviewed-by: Miklos Vajna <vmiklos@collabora.com> Tested-by: Jenkins