<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add an Outline View layout and editing mode to Writer"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=38093#c133">Comment # 133</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add an Outline View layout and editing mode to Writer"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=38093">bug 38093</a>
from <span class="vcard"><a class="email" href="mailto:cougar.b@gmail.com" title="Cougar Brenneman <cougar.b@gmail.com>"> <span class="fn">Cougar Brenneman</span></a>
</span></b>
<pre>There's a lot of editing that I like to do in outline view in Word and in WPS
Office, when I was using that. However, during the process of demoting or
promoting content, you should be able to lock the content at the moment you try
to demote or promote by making it temporarily read-only during the process.
In both Word and WPS Office, it appeared to me as a user that this was how it
worked, whether using keyboard commands or when you click the button to drag
and drop the content at a new level. If selecting a heading for
demotion/promotion automatically also selects the entire tree below that
heading, read-only during drag, and releasing it to be edited after it is
dropped at its new level (or at its new location), those would prevent the
content from being corrupted while it was being moved.
(In reply to Heiko Tietze from <a href="show_bug.cgi?id=38093#c130">comment #130</a>)
<span class="quote">> (In reply to Jim Raykowski from <a href="show_bug.cgi?id=38093#c129">comment #129</a>)
> > Making outline mode a read-only feature avoids these problems.
>
> Doesn't this solution cripples the functionality too much? Use case is to
> temporarily hide (meaning collapse) distracting chapters and continue
> writing. Read-only makes it a just browse-through-document thing. I would
> rather accept the shortcomings and file a ticket so it can be solved later.
> For example by making just the collapsed section read-only (probably not so
> easy).
>
> So my take: Commit Early, Push Often. And involve the users in the
> iterations (38 people on CC of that many never build from source but might
> try the nightlies).</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>