https://bugs.documentfoundation.org/show_bug.cgi?id=126878
--- Comment #9 from Regina Henschel <rb.henschel@t-online.de> ---
(In reply to Heiko Tietze from comment #8)
The cloud object is a custom shape, and while it's possible to create
similar objects with more or less bumps it won't be as flexible as in
AutoCAD (see also bug 101862). You can also convert the object into a
polygon and modify the points though placing the individual points with a
bezier relation to the neighbors is not possible. We have to stick to the
open document format. Of course it would be possible to add a function that
generates a cloud-like polygon, though the number of users who benefit is
limited. On the other hand, it would be a big step forward if realized as
brush (see bug 90045) - this idea might be too far-fetched.
Any other ideas, Regina?
Such object can be saved in ODF as path object or as custom-shape. What
manipulation with the object are done after it is first time generated?
If an immediate realization is needed, I would do it via macro. At least the
way from the outline of rectangle or ellipse to a sequence of arcs is not hard.
Although I would not use real arcs but simple Bézier curve segments.
It is not a question of ODF, but a problem of providing a generating tool.
Besides a conversion tool also a new kind of freeform line might solve the
request.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 126878] Revision Cloud · 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.