Yes, it is my intention that the user can drop a state within another
(non-composite) state and then the containing state automatically has
a region added and becomes composite.

The other things currently missing in the state diagram for UML2 is
the concept of a statemachine having a region. The states cannot be
placed directly in the sattemachine but should be placed in the region
that is owned by the statemachine.

If you look at the current implementation in UML2 mode I think that is
why states are not appearing in the XMI even though they are drawing
on the diagram.

Aside from this and the composite state issue I think state diagrams
for UML2 are pretty much complete.

Regards

Bob.

On 9 May 2011 12:36, Michiel van der Wulp <[email protected]> wrote:
> On 09-05-11 12:58, Bob Tarling wrote:
>> In UML2 there is only a State metaclass for both simple state and
>> composite state. That state has a boolean isComposite ...
>> FigVertex will alter its behaviour depending on the value of
>> isComposite so that it can act like either of our current
>> FigSimpleState and FigCompositeState classes.
> Hi Bob,
> Great!
> Can we (later) add the functionality that you drop a state on a UML2
> state with isComposite=false and have the isComposite turn to true
> automatically?
> I hope your architecture will allow that.
>
> For the end-user there will be no difference any more between simple and
> composite states. Ha, this is actually a good improvement in UML2 :-).
>
> Michiel
>
> ------------------------------------------------------
> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2733018
>
> To unsubscribe from this discussion, e-mail: 
> [[email protected]].
> To be allowed to post to the list contact the mailing list moderator, email: 
> [[email protected]]
>

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

To unsubscribe from this discussion, e-mail: 
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email: 
[[email protected]]

Reply via email to