From d9cd177b9b08d454882dd77ffeb825a184a1b540 Mon Sep 17 00:00:00 2001 From: Miklos Vajna Date: Tue, 16 May 2023 08:31:21 +0200 Subject: sw floattable: disable UI if the frame is chained already TextFrames can be chained and we look at those fly frames as shapes. In this case, we should not offer the "split fly" functionality, which makes sense only when the fly frame is considered as a floating table. The combination of these two features have no use-case and it would just cause trouble when exporting to Word formats. Fix the problem by making SwFramePage::Reset() more strict: it already only allowed fly split for the case when the content was a single table, but now it also requires no chaining. The other way around (split fly -> no chain) still needs doing. Change-Id: I06c240209a3a26519a5df953e22c9ee1b54aed34 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151822 Reviewed-by: Miklos Vajna Tested-by: Jenkins --- sw/qa/uitest/data/chained-frames.odt | Bin 0 -> 10241 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 sw/qa/uitest/data/chained-frames.odt (limited to 'sw/qa/uitest/data') diff --git a/sw/qa/uitest/data/chained-frames.odt b/sw/qa/uitest/data/chained-frames.odt new file mode 100644 index 000000000000..281e06520e27 Binary files /dev/null and b/sw/qa/uitest/data/chained-frames.odt differ -- cgit