[Bug 171023] Replace faint dashed line on page breaks by inline annotation
https://bugs.documentfoundation.org/show_bug.cgi?id=171023 Heiko Tietze changed: What|Removed |Added CC||[email protected] --- Comment #8 from Heiko Tietze --- Some ideas to implement: In sw/source/core/text/porrst.cxx SwTmpEndPortion::Paint() draws the pilcrow (CH_PAR), yet only if there are characters. rInf.GetTextFrame()->GetBreakItem(); is some function but we need to check the next/previous node to amend the correct pilcrow. SWPageFrame's GetPageDesc()->GetName().toString() could be used for the page style name. Something for you, Justin? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171023] Replace faint dashed line on page breaks by inline annotation
https://bugs.documentfoundation.org/show_bug.cgi?id=171023 --- Comment #7 from [email protected] --- Yes - either make it more easy to see/obvious with the off-page dashed line, or add in a way to see it when the "Toggle Formatting Marks" option is enabled, just like in M$ Word, when the similar toggle is enabled, as can be seen in the video link I provided. What is better about LO Writer is that the page break does not require toggling the formatting mark button, but it is just not very visually obvious for those used to the M$ Word method of seeing inserted page breaks, section breaks, etc. (I would guess a large percentage of those converting over to LO Writer are coming from M$ Word). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171023] Replace faint dashed line on page breaks by inline annotation
https://bugs.documentfoundation.org/show_bug.cgi?id=171023 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Keywords||accessibility Summary|Enhancement Request: LO |Replace faint dashed line |Writer inserted manual page |on page breaks by inline |break visualization |annotation |improvements| Status|UNCONFIRMED |NEW CC||[email protected] --- Comment #6 from Heiko Tietze --- So you mean the inline annotation with the idea that these faint blue line we use is easy to overlook. Let's treat this as an accessibility issue. -- You are receiving this mail because: You are the assignee for the bug.
