https://bugs.documentfoundation.org/show_bug.cgi?id=45789
--- Comment #56 from Lionel Elie Mamane <lionel@mamane.lu> ---
(In reply to Howard Johnson from comment #54)
No really, the more important bug I think, is that the LO source code is
mostly too hard to work on.
MY QUESTION: Are code comment-only commits (i.e. comments w/o any code
changes) welcome to the powers that be here?
I expect so. I expect the right place to discuss that is the development
mailing list at https://lists.freedesktop.org/mailman/listinfo/libreoffice
2) As for THIS bug, and having used database report writers (plural)
with CanGrow and CanShrink type features, I am definitely of the opinion
that BOTH of these properties are required, not just AutoGrow, and need
to be added to all controls.
Yes, the way I was suggesting this to be implemented is actually equivalent to
setting both "CanShrink" and "CanGrow". Setting it per-row can be done
relatively easily with the current infrastructure. Setting it per-control
requires a deeper redesign of report builder, or a new feature in ODT/Writer.
Report builder now "just" creates an ODT document, and Writer does all the
actual layouting. So per-control would require that *Writer* support the
feature of "autogrow" (which it calls "optimal row height") per cell, and not
only per row.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 45789] automatic row height in reports · 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.