[Bug 161972] Inserting new comment in Calc disables the "show all comments" setting

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #9 from ady <adylo811517 at gmail.com> ---
(In reply to Heiko Tietze from comment #8)
> How about a tri-state toggle, and better naming of the command (bug 140615)?
> 
> View > [x] All Comments
> * all shown, create visible
> View > [ ] All Comments
> * all hidden, create hidden
> View > [/] All Comments
> * some hidden, create visible

Let's recap. The current menu entry is working correctly; there is no bug
there. The problem is that a user might not understand the effects of the shown
toggle ON/OFF.

The proposed tri-state toggle in comment 8 doesn't solve the potential slight
temporal misunderstanding of the current behavior of the toggle status, and
worse, it blocks (i.e. does not allow) the current status behavior, which is:

 [x] Whichever the prior status (shown/hidden) of any comment in the
currently-shown worksheet, now show (un-hide) all the _current_ comments in it;

 [ ] Some comments might be hidden;

... and with both statuses, newly created comments are initially hidden (with
its reasoning as explained in comment 3).


In case someone is not seeing the detail, the proposed tri-state does not allow
the current behavior.

Instead of changing the meaning and effects of the menu entry, and even
blocking the current behavior, the solution is to improve the documentation
(Help Content) with one paragraph, explaining the meaning of the toggle
(ON/OFF) with better wording. If a user wants every single (new) comment to be
shown, then that user can create (i.e. insert) them and then act on the current
menu entry, once.

I still see no good reason to change the current behavior, and even worse,
blocking it. If the source of this "problem" is lack of intuitive
meaning/effects of the menu entry, the proposed tri-state does not improve its
(intuitive) understanding at all, and better documentation would be needed
anyway. Instead, just improve the documentation of the current behavior,
without the need to over-complicated menu entries (which – worth saying it
again –  blocks the current behavior instead of only adding possibilities to
the current one).

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