Issue 42432 - TOC is not movable when created on the first line
Summary: TOC is not movable when created on the first line
Status: CLOSED DUPLICATE of issue 25280
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 1.1.4
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 42785 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-02-10 14:57 UTC by isr81
Modified: 2021-08-31 20:34 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
show two TOC's. one movable and one not movable (5.99 KB, application/vnd.sun.xml.writer)
2005-02-10 14:58 UTC, isr81
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description isr81 2005-02-10 14:57:25 UTC
When creating a table of contents on the first line of a document, you can't
insert a line break before it, as you can do for TOC's located elsewhere.
Tried Alt+Enter as it works for sections in similar situtations but no luck.
Comment 1 isr81 2005-02-10 14:58:39 UTC
Created attachment 22420 [details]
show two TOC's. one movable and one not movable
Comment 2 michael.ruess 2005-02-10 15:52:24 UTC
MRU->OS: a TOC is a kind of protected section, thus Alt-Enter should also work
there. Please have a look, if this could be solved for 2.0.

Put ES on cc of this.
Comment 3 Regina Henschel 2005-02-10 17:57:42 UTC
I think, it's duplicate to issue 25280.
Comment 4 eric.savary 2005-02-11 08:16:31 UTC
The TOC must be write enabled (first tabpoage of the index dialog: "Protected
against manual changes")

*** This issue has been marked as a duplicate of 25280 ***
Comment 5 eric.savary 2005-02-11 08:16:51 UTC
closed
Comment 6 isr81 2005-02-11 14:38:59 UTC
You are, right, it's the same case as Issue 25280

But I believe it's not practical to chenge the protection so as to move the toc.
Besides, when you want a protected toc, and want to create a new line before it,
you should unprotect it, create two(!!) new lines and protect it again. If one
line is created and something is typed in it, protecting the table leads to data
loss.

I thing the best way is to be treated as sections. Alt+Enter should create a new
line without changing protection.

thanks
Comment 7 eric.savary 2005-02-11 15:20:55 UTC
I don't follow you on your argumentation.

Why is a TOC protected by default?
TOCs are always generated automatically.
Every update of a TOC delete the modifications the user has made manually.
So, the meaning of the default protection is NOT to protect the TOC's content
but to prevent the user from editing it (because those changes would get lost
with each update).

In other words: a protected TOC will always render the settings defined in the
TOC dialog. An unprotected TOC is an advanced feature, wiich allows the user to
customize the automatically created content of a TOC.
Thus unprotecting a TOC gives more flexibility (Ex: setting the cursor in it and
insert new lines before) and protecting a TOC gives the user the guarentee his
TOC will always look the same (even if updating).

So I don't understand your point because:
- I created my TOC automatically, I like it like it is
- I unprotect it to insert new lines
-> nothing gets lost. After updating an unprotected TOC, This won't look
different from the protected TOC.
Comment 8 isr81 2005-02-12 01:10:37 UTC
Ok, I understand the procedure you are talking about. Of course, as you say, you
don't protect the data you enter anymore. If accidentally you protect the toc
you lose the data.
One way that you can be sure of your data is
1. Create the TOC
2. Unprotect it
3. Use Alt+Enter (not just Enter) twice, so as to create a new line outside the
toc's region (and before it)
4. Protect the TOC, so as to avoid accidental loss.

What I am suggesting is the ability to use Alt+Enter on the protected TOC (as in
protected sections), so you can skip this procedure and be safe about the data
you enter (I understand it is silly to protect the toc when having data entered
in it's field, but you can't be to sure).

Hope I have become more clear.
Comment 9 Oliver Specht 2005-02-13 14:36:28 UTC
Target changed to Later (not broken)
Comment 10 michael.ruess 2005-02-15 07:18:03 UTC
*** Issue 42785 has been marked as a duplicate of this issue. ***
Comment 11 mantas 2005-09-27 10:18:37 UTC
Problem is not in protecting or unprotecting TOC.
If user inserts TOC on the first line of a document, then he can't insert a line
or page break or write a text *before* it (not in the TOC, but *before* it), but
if he inserts TOC on second or later lines of a document, then he can insert a
line, page break or write text *before* the TOC.
Comment 12 Marcus 2017-05-20 11:24:57 UTC
Reset assigne to the default "issues@openoffice.apache.org".
Comment 13 Marcus 2017-05-20 11:26:01 UTC
Reset assigne to the default "issues@openoffice.apache.org".
Comment 14 oooforum (fr) 2021-08-22 08:39:03 UTC
According with previous comments

*** This issue has been marked as a duplicate of issue 25280 ***