Apache OpenOffice (AOO) Bugzilla – Issue 70991
row height extends to page size when dragging border with mouse in table breaking across pages
Last modified: 2017-05-20 11:25:57 UTC
In the OOo 2.0.3 change the height of the row (the last row of a table be divided into two pages.)make the row is full of the page. The bug can be described as follows : 1. build a new word-processing document 2. insert a table 3. Input Enter(s) in the random cell of the last row of the table and make the cell be dvivded into two pages. 4. locate the cursor in another cell of the first page. 5. change the height of the last row of the second page by Mouse. you will find the row is full of the second page. I have repaired the bug.
MRU->FME: insert a table into document and add content to the last row so that the table braks onto next page. Place Cursor in a different cell on page 1. Now change the height of the last row by dragging the bottom table border -> row now covers whole page
I have repaired the bug.It is something wrong with file ndtbl.cxx.
fme->liutao: Sounds good. Can you please attach the patch to this issue?
Created attachment 40352 [details] the patch of this bug
fme->liutao: Thank you for your support. I had a look at your patch. Please correct me if I'm wrong, but in both cases, if and else, the SetLastRowAllowedToChange flag at the table will be set to true, so basically your patch replaces rFill.SetLastRowAllowedToChange( !pTab->HasFollowFlowLine() ); with rFill.SetLastRowAllowedToChange( true ); The meaning of the SetLastRowAllowedToChange flag is this: If the last row of the current table frame is split across two pages, it should not be allowed to change the height of the last row. Your patch might work in your scenario, but I think this issue needs some deeper digging.
setting the issue type to patch reassign back to liutao for rework as fme suggested. set taget to not determined as it is of type patch now.
added myself to CC
liutao, this patch seems to be insufficient. Can we expect that it will be reworked? Or can we close this issue?
Matthias, MRU confirmed the Issue. It cannot be closed due to a failed patch was proposed. -> Reset to defect Is 3.0 a acceptable target? Peter
I think compared to other defects this issue doesn't look so important. As we already have several hundred defects for target 2.x+3.0 I think "OOoLater" is more appropriate as we most probably will not have time to work on it. Of course if other developers like to work on this issue and come up with a patch we will help to integrate it.
Reset assigne to the default "issues@openoffice.apache.org".