https://bugs.documentfoundation.org/show_bug.cgi?id=126546
--- Comment #36 from Adalbert Hanßen <[email protected]> --- (In reply to ajlittoz from comment #34) > ... > > Also, when I split a paragraph, I expect *all* layers to keep their present > settings. I agree *if there are characters right to the split point*. When sketching some document, I start with headings only. In order to add on, I enter a space before the paragraph mark and split before that space, then a headline of the same level is created (otherwise it would continue with TextBody, the default after any heading in my default stylesheet). I remove the space immediately when actually writing the next heading. If I wnat to change levels, I look up at the display of the headline-level and press <Ctl-number> as needed. The general rule seems to be: Continue formatting in the same way as *to the left of the insertion point*. This rule is broken by <Return>. normal*bold* in a line, adding xyz after normal continue normal. It yields normalxyz*bold* However: pressing <Return> and continue writing xyz yields normal *xyzbold* Try it! > > ... A paragraph can be associated with a list style. There are two > schools for this: the style one where the list style is declared in > the PS, making the PS dedicated to list item, and the DF one where > a toolbar button is pressed to turn the paragraph into a list item. > When Enter is pressed, most users expect the "list attribute" to > remain active so that the next item is entered without any other manual > operation. agreed for the next line becoming a list item. You can easily terminate the list property by pressing <Enter> twice. You can easily prevent a number or bullet by pressing <Backspace> after <Enter>. Getting rid of formatting can be more difficult since it can stem from DF or CS. >... > PS: (see end of comment 33) the present formatting state is reflected in the > toolbar buttons. Of course, this doesn't tell which layer activated it (PS, > CS, DF). But colouring the button might be impossible because of the > "themes". Status colouring would override theme colouring (or conflict with > it) agreed: Then we need other means to see it a glance. Two years ago, Heiko Tietze made a nice proposal: https://design.blog.documentfoundation.org/2019/11/05/proposal-to-conveniently-highlight-and-inspect-styles-in-libreoffice-writer/ -- You are receiving this mail because: You are the assignee for the bug.
