Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365405 - [StateMachineDiagram] Behaviours (Entry,exit,do) on states should have their own mechanisms
Summary: [StateMachineDiagram] Behaviours (Entry,exit,do) on states should have their ...
Status: REOPENED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ansgar Radermacher CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 365404
  Show dependency tree
 
Reported: 2011-12-02 05:19 EST by Arthur Daussy CLA
Modified: 2017-08-02 11:37 EDT (History)
2 users (show)

See Also:

Attachments
Model in which the bug can be done (3.94 KB, application/zip)
2012-01-13 05:38 EST, David Rabely CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur Daussy CLA 2011-12-02 05:19:47 EST 
The following actions from the figure should be available for behaviours (entry,exit and do) on states:
 -> Be selectable
 -> Be navigable
 -> Be deletable (visually)
 -> Be draggable
Comment 1 Arthur Daussy CLA 2011-12-02 05:22:34 EST 
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..).
Comment 2 Arthur Daussy CLA 2011-12-02 06:02:27 EST 
Committed on the branch 0.8.X.
Not reported on trunk yet (no builds available)
Comment 3 Arthur Daussy CLA 2011-12-07 09:08:30 EST 
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.
Comment 4 Arthur Daussy CLA 2012-01-09 05:17:30 EST 
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...
Comment 5 David Rabely CLA 2012-01-13 05:38:53 EST 
Created attachment 209442 [details]
Model in which the bug can be done
Comment 6 Arthur Daussy CLA 2012-01-17 10:39:10 EST 
The state figure should a an internal activity compartment (specify UML 2.4).