|
|
| Re: Partition in Activity Diagram [message #602199 is a reply to message #602009] |
Tue, 29 June 2010 07:31   |
 Vincent 
Messages: 35
Registered: December 2009 |
Member |
|
|
Hello,
for now, Activity Partitions do not work correctly in the Activity Diagram.
You can create a node which corresponds to an Activity Partition, but it will not be able to contain nodes (not currently implemented).
If you do so, I suggest you use the right click menu "Format>Order>Send To Back", to keep it behind every other node.
Thanks to the group management feature, nodes will be assigned to partitions by placing them above it, but for now, they will not be graphically contained by it. (thought, you will be asked by a popup whether you want the nodes to be graphically contained, which is not possible yet)
I suggest you try and create your partitions latest, then send it to back to have all your nodes above.
The group management feature should automatically assign the nodes to the partition.
I'm afraid this bug will not be corrected for the next release.
Regards,
Vincent.
|
|
|
|
| Re: Partition in Activity Diagram [message #602526 is a reply to message #602009] |
Tue, 13 July 2010 06:53 |
Vincent
Messages: 35
Registered: December 2009 |
Member |
|
|
Vincent H wrote on Tue, 29 June 2010 03:31
> You can create a node which corresponds to an Activity Partition, but it will not be able to contain nodes (not currently implemented).
>
> ...
>
> I'm afraid this bug will not be corrected for the next release.
Meanwhile, it has been implemented... So now, you can create nodes in an Activity Partition, though you may have difficulties to drag them out of it after (this is a known bug, which you can work around by droping in an intermediate StructuredActivityNode which does not contain the node, before droping it in its original place out of the partition).
Nabil wrote on Mon, 12 July 2010 14:39
> Hi,
>
> Thank you for answering, now it's enough clear for me. Do you know if there is others differences between uml papyrus implementation and uml omg standard? (I hope I am enough clear in my question...)
Sure you are clear, yet not precise enough.
Papyrus tries to be as close to the UML specification (OMG standard) as possible.
Some features have not been implemented due to a lack of time (and considered as bugs). Some others because they are only shortcuts and we considered they did not have the priority, though we do not eliminate the possibility of implementing them later.
I could not list all of them right here and right now. The best way to know for a particular element is to ask as you did when you encounter problems.
For what I can tell aboutthe activity diagram (this is not a complete list):
- Activity groups have been very quickly developped and are not fully mature. You may encounter bugs among them (do not hesitate to report them on the bugzilla if you find some which are not already referenced).
- Triangle symbol for exception flows is missing.
- Only most usefull actions have been implemented.
- Shortcut for representing two pins around an object flow in a same rectangle has not been implemented (see http://www.eclipse.org/forums/index.php?t=msg&th=170835& amp;start=0&)
Regards,
Vincent.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02269 seconds
] 
Search
Help
Register
Login
Home
