https://bugs.documentfoundation.org/show_bug.cgi?id=142446

--- Comment #12 from Jim Raykowski <[email protected]> ---
(In reply to j.a.swami from comment #11)
> Everything on the canvas seems as expected, with one exception:
> 
> At 1:38 I don't understand why unfolding everything (in the canvas) to level
> 5 also displays the (no-level) text under level 3. I would have thought that
> this text would remain undisplayed and all we would see would be the
> subheads at all levels up through 5. 
> 
The point being made there is to show that this works not only for folded
content outline level limiting. The outline content was unfolded and then the
limit level was below level 3 then above which showed the unfolded outline
content as it was before limiting. 

> I do have some other questions, though.
> 
> First, in "Options" (at the start of the video) I'm not sure what checking
> or unchecking "show sub levels" does. A hierarchical tree is all about
> various levels and sublevels. And I would think that whatever levels and
> sublevels we see at any given time would be in response to specific choices
> made as we go along. So what exactly does "show sub levels" do? I don't
> understand.
"Include sub level" means sub levels are treated as content of parent levels.
So, if the parent is folded then all content including sub level content is
hidden. When sub levels are not being included as content, folding parent
content only folds content to the start of the next outline heading, be it a
sub level heading or a same level heading or a super level heading.   

>From the documentation:

Outline Folding: An extra option (Show outline-folding buttons) is available in
Tools > Options > LibreOffice Writer > View (Figure 5). When this option is
selected, a button with an arrow is visible near any selected heading in your
document. Click on it to fold all text from the current heading to the next
heading. If Include sub levels is also selected, clicking on a heading folds
all text from that heading to the next same-level heading with all its
subheadings.

>  
> Second, I'm not sure about when and how showing or hiding levels in the
> Navigator effects the showing or hiding of levels in the canvas. At 0:34,
> clicking "fold all" in the Navigator clearly folds the entire outline in the
> canvas. But at about 1:13 "Unfold all" seems to unfold only the Navigator
> tree, while the tree in the canvas remains folded. So I'm confused.
>
That was "Expand All", which expands all levels in the Navigator tree. Outline
folding options are located under the "Outline Folding" submenu. Showing and
hiding of levels in the Navigator does not affect the levels shown/hid on the
canvas. The Navigator simply displays the available headings that are in the
document. Folded content headings are not shown because they are not visible on
the canvas. Perhaps it is better for headings that are not visible  to be
greyed out in the Navigator, but that is for a different discussion...

> I'm similarly confused about when showing or hiding levels in the canvas
> affects the showing or hiding of levels in the Navigator. At about 1:13,
> folding everything to Level 1 in the canvas similarly folds the outline in
> the Navigator. But at 1:38, unfolding the outline in the canvas to level 5
> leaves everything in the Navigator folded to level 1.  
>
When there are only Level 1 Outlines shown in the canvas then the Navigator
only displays these because all other outline levels are hidden. This gets back
to graying out headings that are not visible. The Navigator tracks content at
the cursor position. When showing outline content to level 5, the cursor
position does not change, so the highlighted heading in the Navigator does not
change. In default outline tracking mode when the cursor is moved, the heading
under that cursor is highlighted in the Navigator, which will expand the tree
as needed.    

> But again: Apart from the issue at 1:38 (and leaving aside my confusion
> about the Navigator), everything in the canvas looks right to me.
Ok, I'll look the patch over again then put it in the master build so you can
give more first hand feedback.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to