summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@collabora.com>2023-03-07 08:25:56 +0100
committerMiklos Vajna <vmiklos@collabora.com>2023-03-07 08:25:06 +0000
commit5d5dca66e17c90e20197d0d76113254b13ff0bb7 (patch)
tree60014ce70f1f22a41a92b5927c15dfa38fcfb497 /README.md
parent503b14eee1f05e987fb415d25da1086defe8c772 (diff)
sw floattable: grow the print area as well in SwFlyFrame::Grow_()
The bugdoc should be of 3 pages, but the last for of the floating table went to the 3rd page. The reason for this was that SwTabFrame::MakeAll() calculated nDistanceToUpperPrtBottom, then determined that the upper has to grow, and called GetUpper()->Grow(LONG_MAX, /*bTest=*/true). Now this growth was less than what would be possible, because a previous invocation of SwFlyFrame::Grow_() increased the frame area (with margins) but not the print area (with margins). This meant that the frame can't grow too much because its frame height is already 7044 twips but its print height is only 548. This combination of "not enough inner space" and "can't grow too much, either" resulted in moving the last row to an unwanted 3rd page. Fix the problem by not only increasing the frame height but also the print height in SwFlyFrame::Grow_(), this keeps the last row on the 2nd page, like Word does. Change-Id: I7850b54b030c42034e0a117d52d2148fa6ba2f83 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/148373 Reviewed-by: Miklos Vajna <vmiklos@collabora.com> Tested-by: Jenkins
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions