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

Bug 345881

Summary: [StateMachine Diagram] Changing the property "kind" of a pseudoState, only the outline is changed
Product: [Modeling] Papyrus Reporter: Fabien Gautreault <fabien.gautreault.ext>
Component: DiagramAssignee: Camille Letavernier <cletavernier>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: charles, jeremie.tatibouet, papyrus-bugs
Version: 1.1.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: SR3

Description Fabien Gautreault CLA 2011-05-16 04:10:48 EDT 
Build Identifier: 20100617-1415

[StateMachine Diagram] When user change the property "kind" of a pseudoState, only the outline is changed, not the graphical part. It could have been a problem of refresh but when user close/reopen the model or close/reopen papyrus, the graphical part still didn't change and is not coherent anymore with outline.

Reproducible: Always

Steps to Reproduce:
1.create a pseudoState
2.change the property "kind"
3.Only outline is changed
4.Close/reopen model or papyrus, nothing change
Comment 1 David Servat CLA 2011-05-19 10:24:06 EDT 
True. In fact, the property "kind" should not be changeable through the property view. It is prone to error as pseudostates vary a lot e.g. from a EntryPoint which sits on the side and is owned by the statemachine to an initial pseudostate which is owned by the containing region.

Should be corrected in the property view generated for pseudostate.
Comment 2 Ansgar Radermacher CLA 2013-04-02 09:30:01 EDT 
Camille, can you please constrain changing the "kind" attribute of the pseudo state. There are still some changes that would be useful, for instance toggling between deep and shallow history state, but for the moment I propose to disable changing the kind completely.
Comment 3 Jeremie Tatibouet CLA 2015-11-09 12:51:35 EST 
The bug is still there. If I click on an ExitPoint that is on the edge of a composite state I can change the kind of this latter to "junction". This affects the diagram as well as the property view. Both views become inconsistent while the semantic model (the abstract tree) is still correct.

If the model is closed and re-open, the diagram and the property view are still both invalid.
Comment 4 Camille Letavernier CLA 2015-11-10 06:38:59 EST 
The StateMachine Diagram doesn't support the change of Kind for pseudo-states. This can't be easily fixed

The easiest (partial) fix would be to prevent the user from changing the Kind of a pseudo-state, but we cannot remove this possibility from e.g. the Advanced tab of the properties view. We should also ensure that it is possible to create all kinds of PseudoState from the ModelExplorer, since it wouldn't be easily possible to change their kind afterwards
Comment 5 Camille Letavernier CLA 2015-11-10 08:07:27 EST 
Pseudostate#kind is now read-only in the properties view

Commit 9af3696 (Master) and 8fd8c23 (Mars)