[Bug 163537] Frame boundary visibility is now controlled by View > Formatting Marks

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #12 from lomacar at gmail.com ---
(In reply to V Stuart Foote from comment #11)
> (In reply to RGB from comment #7)
> (In reply to lomacar from comment #8)
> (In reply to Heiko Tietze from comment #9)
> > This was introduced for bug 131253 by Justin with the comment
> >
> 
> Nope. Reviewing bug 131253 and commit [1], Justin's logic was sound and
> *was* well reviewed. 
> 
> It explicitly addressed the non-printing visual aids being placed around
> frames of inserted images.
> 
> Disagree with Heiko's take, NPC has not controlled just single glyph markers
> since the 3.6 release (where it already toggles between showing the page
> margin corner marks and full margin lines), and at 5.0 release its labeling
> in UI changed from 'Non-printing Characters' to 'Formatting Marks' [2] to
> better reflect its scope.
> 
> Still room for additional effort for user configuration of controls (tb
> button|menu|module options)--but having the "subsidiarylines" toggle with
> 'Toggle Formatting Marks' (.uno:ControlCodes) is functional and suited to
> task.
> 
> 
> =-ref-= 
> [1] https://gerrit.libreoffice.org/c/core/+/165294
> [2] https://gerrit.libreoffice.org/c/core/+/28742

I couldn't disagree more. This is a major issue to how I and many others work.
There absolutely must be a way to toggle Non-printing Characters separately
from boundaries. They way it worked before was fine! Why change it? There was
no reason to do so. And it's a stupid idea to require users to turn on two
options in order to see something. How is the average user supposed to figure
that out? Especially when one of the options is so unintuitive? When someone
turns on View > Text Boundaries, they expect to see text boundaries!

Formatting marks should be changed back to Non-printing characters. Why was
that even changed? Why do the page boundaries change with that option? That
also feels like a bug. No other software ties non-printing characters together
with boundaries or guides or grids or any kinds of lines.

The major difference between these things is that Non-printing characters can
change the flow of the document because they are actually characters in the
text. This must be treated separately from lines that control the flow of text.
As I said before, it is rare that anyone ever needs to look at non-printing
characters, but it is normal that people need to see boundary lines.

If this isn't fixed I am going to have to downgrade LibreOffice and never
upgrade again. How do these decisions get made? To me it's an obvious bug, but
let's put it to a vote somewhere if we have to.

-- 
You are receiving this mail because:
You are on the CC list for the bug.