https://bugs.documentfoundation.org/show_bug.cgi?id=120825
Heiko Tietze <tietze.heiko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
CC|libreoffice-ux-advise@lists |tietze.heiko@gmail.com
|.freedesktop.org |
Keywords|needsUXEval |
--- Comment #4 from Heiko Tietze <tietze.heiko@gmail.com> ---
Basically I like the idea to improve consistency and having bucket modes on
more functions is worth a second thought. But OTOH it's not a very common
feature and would rather be used by freaks. And as Stuart pointed out we have
exactly this mode but only at the sidebar. So I'm resolving as WFM.
Thing is that bold, italic etc. at the toolbar format directly and don't apply
a character styles. A problem raises also from the fact that some properties
are toggled and the bucket mode would not only set a property but also unset at
the same time depending on the previous target state.
Last but most important I struggle a bit with the use case. The freaky bucket
mode changes a property in a batch process, meaning you apply it to many
items/words. And I doubt that this is really the usual workflow.
But thanks for your input. Even freaky ideas are always welcome.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 120825] proposal to apply character styles : with 'paint bucket' cursor, as for colors. · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.