> I'll look at some other tools and see how they manage this.

I just looked at Magic Draw Community Edition 15.5 (for UML2.?).
Apologies for the draw at description. It is complex and probably
worth checking it out for yourselves.

I think the property panel for Message in MD includes the fields for
the Action rather than showing a separate panel as we do. The fields
in the property panel change when the user changes the "Message sort"
field from one type to another.

For all message types a sequence number is displayed. Below is how
they defer depending on type.

Bob.

synchCall and asynchCall
===================
For message sort of "synchCall" and "asynchCall" there are the
following properties on the message panel that appear to affect the
notation:
Guard
Target
Operation
Arguments

This translates on the diagram as [guard]target.operation(argval1, argval2)

There is an attribute for message name but this does not appear on the diagram.

The square brackets only appear if there is a Guard.

The dot only appears if there is a Target.

The round brackets are always there even if no other information is supplied

The peculiarity here is that it appears that the user can edit the
diagram label. However any attempt to do so does not effect those
properties. Instead it will set the message name to whatever the user
types in the label and then revert the label back to its previous
state.


"reply", "createMessage" and "deleteMessage"
==================================
For message sort of "reply", "createMessage" and "deleteMessage" there
are the following properties that appear to affect the notation:
Guard
Target
Name
Arguments

This translates on the diagram as [guard]target.name(argval1, argval2)

Essentially this acts the same as synch/asychCall except that there is
no property field available for operation and the name property takes
its place. Again whatever the user types on diagram will only replace
the name.

The display difference is that round brackets are only displayed if
there are arguments.



For message sort of "asynchSignal" there are the following properties
that appear to affect the notation:
Guard
Target
Name
Signal
Arguments

This translates on the diagram as either
[guard]target.name(argval1, argval2) or
[guard]target.signal(argval1, argval2)

If a signal property is set then that is used in preference otherwise
it falls back to name.

Editing on diagram is once more only changing the name property.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=984757

To unsubscribe from this discussion, e-mail: 
[[email protected]].

Reply via email to