At 19:15 23/01/2008 -0600, Barbara Duprey wrote:
I've asked before, but no answers yet, so I'm trying again. Do other people think it's a bug that cells of a complex row (with cells merged, vertically in this case) can split across pages when the table properties say that rows are not to be split? This just started happening recently, I think in version 2.3, and I haven't found an acceptable workaround. This definitely gets in my way very regularly, the process I used to use is now broken.
For the benefit of someone who asked for an example, here is my explanation of the problem. Suppose you create a table with more then one column and more than one row. Then you merge two or more cells vertically in one or more columns. So far, so good. Now you remove the default tick from "Allow row to break across pages and columns", with the intention of keeping each cell unbroken on one page or another. The problem is that Writer, whilst keeping the original cells intact, appears to maintain what is effectively a hidden boundary between the merged cells and - unhelpfully - to allow the merged cell to break across pages at this boundary.
Yes: if it prevents you doing what is intuitive and what you need, it probably is a bug.
I think there is a workaround of sorts. Instead of merging cells vertically, first create a table with a single row spanning the rows that you would have (partially) merged. Then create a new, nested table in each of the columns in which you do not want the cells merged, thus creating the extra rows within those columns. If you now set the containing table not to allow rows to break, you can sometimes get Writer to behave as you want. (This setting seems to carry across to child tables in unclear ways.) I found that (sometimes? always?) this didn't work if the first row happened to be the one that needed this treatment, but I could get around this by adding an extra row before the real first row and shrinking this to an arbitrarily small height. I haven't tested this exhaustively, of course, so I don't guarantee that it will work generally.
I trust this helps. Brian Barker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
