Version: (using KDE Devel) Compiler: gcc 2.95 OS: Linux From Volker Siepmann I'd like different kinds of messages in sequence-Diagrams (at least call, return, and create)
Yes, and "focus of control". All the notations defined in the UML Notation Guide 03-03-01 would be good: Section 3.62.2 Activation --> Notation Section 3.63.3 Message and Stimulus --> Presentation Options
And destruction, of course, Section 3.61.2 Object Lifeline --> Notation
Synchronous and asynchronous are now possible. Destruction is effectivly possible. Not sure how to do the programming for creation, will think about it. Concurrent objects should also be possible. Branching would be difficult.
*** Bug 53364 has been marked as a duplicate of this bug. ***
Just to be nit-picky (and because my professor has expressed a *slight* disliking that diagrams I turn in would be non-standard from his point of view) - Asynch messages should only be half arrow - Asynch messages are usually (??) encassed within the object life-line. Currently asynch messages are shown in the dashed portion of the line.
> - Asynch messages are usually (??) encassed within the object life-line. > Currently asynch messages are shown in the dashed portion of the line. I don't understand this part, what does encased within the object life-line mean? Thanks
Ah, nevermind. The dashed line (called the lifeline) becomes a tall rectangle(called an activation) whenever the object is in use. The default size for this box is relatively small and I didn't notice we were able to resize it at will. The half-arrow problem still stands though.
Actually Jesse's professor is out of date! From UML 1.5 spec: Stick arrowhead ----> Asynchronous communication; that is, no nesting of control. NB UML 1.3 and previous versions included a half-stick arrowhead notation in addition to the stick arrowhead notation. This notation has been removed because the semantic distinction between the two was subtle and confusing.
LOL! Wow. I think I'll humbly step away from my computer now. My above comments can be completely disregarded :) I was also looking at an out of date spec. oh the shame :(
*** Bug 92907 has been marked as a duplicate of this bug. ***
Creation messages are implemented.
Closing this as the most important message types are now implemented. Please create a new, more specific entry if anything else is missing.