After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 451222 - Resize UML elements
Resize UML elements
Status: RESOLVED OBSOLETE
Product: dia
Classification: Other
Component: objects
0.96.1
Other All
: Normal enhancement
: ---
Assigned To: Dia maintainers
Dia maintainers
: 501272 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-26 12:13 UTC by fbab
Modified: 2019-03-20 11:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description fbab 2007-06-26 12:13:26 UTC
Hello,

Thank you for the great work done. Nevertheless I would like to let you know an annoying constraint when drawing UML diagrams. It has been brilliantly expressed in a mailing-list but I did not find it in Bugzilla.

Yours sincerely, fbab.

http://www.mail-archive.com/dia-list@lysator.liu.se/msg03789.html
Hello.
Why are some UML objects resizeable (e.g., node, or large package),
and most others are not (e.g., actor, component). Is it because of
legacy code or simply considered as not necessary? It would be very
nice, if all UML objects are resizeable.
Regards, Sebastian


Other information:
Comment 1 Lars Clausen 2007-08-09 17:12:28 UTC
It is because of legacy code and/or the complexity involved in determining the correct rendering.  Thus it is merely a question of somebody pluggin in the right code.
Comment 2 Lars Clausen 2007-12-03 20:04:59 UTC
*** Bug 501272 has been marked as a duplicate of this bug. ***
Comment 3 sphakka 2013-08-28 13:09:18 UTC
I'd also like to have automatic word wrapping of text fields in shapes, such as state's actions.
Comment 4 GNOME Infrastructure Team 2019-03-20 11:32:45 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/dia/issues/206.