Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 318901

Summary: [StateMachine Diagram] Correction of Pseudostates
Product: [Modeling] Papyrus Reporter: David Servat <David.Servat>
Component: CoreAssignee: David Servat <David.Servat>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: Mac OS X   
Whiteboard:

Description David Servat CLA 2010-07-05 10:36:14 EDT 
Pseudostates are updated along with the palette
Comment 1 David Servat CLA 2010-07-22 10:05:01 EDT 
The situation is in fact a little bit more complex for Pseudostates, because in fact entryPoint and exitPoint should be owned by a StateMachine or a (composite) State. Thus there is a need to constrain the creation of entry/exitPoints as children of State/StateMachine and not as Region, which is currently the case.

Second point is that for the moment these entry/exitPoints are displayed within a Region (this is optional in the norm) the preferred way is to show them on the border, which is coherent with the above point (i.e. being owned by states or stateMachines).

So covering this is a little bit more involved...
Comment 2 David Servat CLA 2010-09-09 10:20:17 EDT 
Entry and Exit Pseudostates now corrected: creation with correct owner (i.e. StateMachine) and border location.

As a result, a customized palette is no longer needed (we use the gmfgen mechanism to set the kind accordingly and dedicated edit part per pseudostates).

Class removed in commom concerned dedicated post palette creation action for pseudostates, which are no longer needed
Comment 3 Yann Tanguy CLA 2010-09-10 17:09:43 EDT 
Invalid @override tag removed in r2685 (nightly build broken).