| Summary: | [StateMachineDiagram] Behaviours (Entry,exit,do) on states should have their own mechanisms | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Arthur Daussy <arthur.daussy> | ||||
| Component: | Core | Assignee: | Ansgar Radermacher <ansgar.radermacher> | ||||
| Status: | REOPENED --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | David.Servat, raphael.faudou | ||||
| Version: | 0.8.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 365404 | ||||||
| Attachments: |
|
||||||
|
Description
Arthur Daussy
In order to do this a refactoring has to been made on the state element. Behaviours ( entry,do and exit) will have their own EditPart. It allow them to have all the requested behaviours (selectable etc..). Committed on the branch 0.8.X. Not reported on trunk yet (no builds available) New solution committed committed on the 0.8.X branch. This solution use trigger on the transaction editing domain without registering MDP Papyrus transactionnal editing domain into EMF regitry. See related bug 365577 for more explanation. Committed on trunk (and branch). There is one know bug concerning this feature which has been describe there in the Bug 368132. Will be corrected soon. Do, Entry and Exit behavior can now be selected as separated component. Which means they can be: -> Used for navigation EditPolicy. -> Hidden -> Dragged and Dropped -> Etc... Created attachment 209442 [details]
Model in which the bug can be done
The state figure should a an internal activity compartment (specify UML 2.4). |