mike scott wrote:
On 12 Sep 2006 at 10:49, Ross Johnson wrote:
...
Hmmm. I'm still not clear what's happening here.
I've cleared the 'protected' setting, and so can make any old changes
to the ToC. However, the 'Insert' checkbox under 'breaks' is /clear/
anyway - even though the ToC immediately follows the break. That
said, having cleared the 'protected' setting, I can now move the
cursor to the start of the table and simply hit bckspc - which seems
to clear the break. That's OK, but if I then /set/ the protect bit
again to prevent accidents, the title "Table of Contents" now appears
twice, once protected, once not. I guess I can live with that, but
it looks like a minor bug.
I don't think you've told us which OOo version you're using. I don't
get this, but maybe there's something else in your document that is
affecting things.
Oooops. 2.0.2; sorry.
Doesn't appear to be any different in 2.0.3.
It gets worse though. I thought I'd start over from an empty document.
Insert a couple of "heading 1" lines, go back to the top, insert ine of
straight text, manual page break, then a ToC. That's OK so far -- a
page with my one line, then a new page with the ToC and the 2 headers.
(Although looking at 'edit para style' for the ToC shows that the
insert checkbox is clear on the text flow sheet.)
Go to the ToC, allow manual changes, then point into the title line,
hit 'home' to get to the start and 'bckspc' to delete the break. The
break goes and the pages collapse into one, and my one line of text is
formatted with the ToC title style and concatenated with that title.
You might expect the ToC title to inherit the style of the paragraph
that it was appended to when you backspaced, which is what happens if a
body text line becomes part of it's preceding Heading after removing the
paragraph break between them - the whole line acquires Heading style,
not body text style.
Insert a newline to separate the two; then go back to the table and
reprotect it. I've now lost my line of text completely, the
documenting starting with the ToC -- worse, 'undo' is greyed out so I
can't get it back.
This really doesn't feel correct behaviour to me!
My initial guess would be that the ToC is a higher level entity than
paragraphs (a special container). So when someone does what you did, I
can imagine that the logic might be that the line of text must become
part of the ToC, rather than mess around pulling text out of the ToC to
format as body text. It also appears that reprotecting the ToC triggers
an update of the ToC. If, rather than reprotecting the ToC, you update
it, you will see the same thing happen - the whole ToC title, including
the line of text that is now part of it, is replaced with the title that
is given in the Edit Index/Table dialog.
...
Actually I'm wrong there - Backspace to remove the Break Before doesn't
do the right thing IMO. With the Break After followed by the Break
Before, it shouldn't join the two paragraphs, and should only remove the
hidden blank page and adjust the page numbers (the second page should
still become page 2/2 because the Backspace should remove the Break
Before and also the associated page number change to "7".)
If you undo all of that to start over but now place the cursor at the
end of the last para on your first page, and press Delete - then once
again the first para of your second page is joined to the cursor para.
I.e. this action appears to remove the Break Before setting of the
following para. This would be ok if there was no Break After in the
cursor para. However, the page number of your second page should then
be "Page 2/2". That is one bug, but there is another bug too IMO.
In the above (Delete) operation, the Break After setting should be
removed from the cursor para rather than the Break Before of the
following para. This should leave the Break Before para intact at the
top of your second page, but it should remove the blank page (that you
only see in print preview) and show your second page number as "Page 7
2/2".
That piece of analysis still seems correct to me though.
Ross
I get the feeling that all this 'break' stuff is just a bit flakey --
sort of works, usually, but breaks (if you'll pardon the pun) rather
easily.
I'm going to check the bug reports and submit one if I can get the time
to better understand what the issues are.
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
