[Libreoffice-ux-advise] [Bug 140820] Should there be a "Default Frame Style", which each builtin Frame Style "Inherits from"?
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Tue Dec 21 12:08:22 UTC 2021
https://bugs.documentfoundation.org/show_bug.cgi?id=140820
--- Comment #14 from Mike Kaganski <mikekaganski at hotmail.com> ---
(In reply to sdc.blanco from comment #13)
> Noticed that FALSE, but did (do) not understand it (and no mention
> in Release Notes), so ignored it.
FALSE is absolutely unrelated. We were discussing the *rename of the button*,
which is what I tried to show there.
> > The tip ...is technically correct, but does not give a tip which values
> > will be used instead.
> Do you have a recommendation/suggestion?
> (I do not know the hardcoded defaults)
"... Corresponding values from parent style, or program defaults if there's no
parent, will be used."
> Alternatively -- see title of this bug -- which is formed as a question.
> If there was a "Default Frame Style" (even if it was just equivalent to the
> hardcoded defaults), then the user would know what happens with "reset to
> parent", plus could modify the values for the "default FS" as needed.
>
> (I understand that there can be multiple style hierarchies, and -none- would
> still be needed, but no obvious problem in relation to the OP -- to improve
> the understanding of what happens when "Reset to parent" is used.)
You mix several concepts freely, and it's very difficult to discuss this way.
*If* you suggest some "equivalent to the hardcoded defaults", then no, -none-
would *not* be still needed. If you propose that "equivalent to the hardcoded
defaults" to be also user-sditable, it's a big change. If you do not propose
that, as you write in the following part:
> (btw, this seems to be how PS is currently handled. All PS inherit from
> Default Paragraph Style in the style hierarchy (where Default PS inherits
> from -none-)).
... then you are just shifting the goalpost, because for default paragraph
style, the button still has unclear (for user) behavior, and you do not fix
anything. Additionally, multiple hierarchies without common root is not a
solution - so suggestion to only provide common parent for "each **builtin**
Frame Style" - would be just a false fix, which would pretend to fix something,
but would keep the same problem for non-builtin styles, as if that improves
things.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Libreoffice-ux-advise
mailing list