Bug 405577

Summary:	[StateMachineDiagram] Display of states is well managed until we add new elements
Product:	[Modeling] Papyrus	Reporter:	Samuel Rochet <samuel.rochet>
Component:	Diagram	Assignee:	Ansgar Radermacher <ansgar.radermacher>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	papyrus-bugs
Version:	0.10.0	Keywords:	usability
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Samuel Rochet

2013-04-12 09:49:42 EDT

[STM] Display of states is well managed until we add new elements. However, if we try to redisplay a state previously hidden, we need to drag&dropp all its elements to redisplay them.
The appearance tab for a sate in the property view should be modified in order to propose display option as is it done for others elements.

Comment 1 Sébastien Gérard

2013-04-15 16:57:43 EDT

Please, details the requirements with more details: what the display option which are cited in the previous comment. Thanks.

Comment 2 Samuel Rochet

2013-04-16 11:05:15 EDT

The proposition is to add in the appearance options of a state an option similar to the label customisation of properties.
This option should enable the display of the graphical content of a state as entry, do or exit behaviors, the list of defered events, etc.

Another possibility can also be to allow the user selecting the elements to display via the "Show/Hide Content" dialog box.

Comment 3 Camille Letavernier

2013-05-07 03:53:44 EDT

The do, entry and exit behaviors are indeed "lost" (i.e. they need to be dropped again) when the state is hidden.

The state compartment should work like Operation or Properties compartment:

- Implement the Show/Hide dialog

Moreover, as Do/Entry/Exit are [0..1] references, it may also be managed with an appearance property.

The State compartment is hidden by default. It should probably be visible by default.

We may also display the Do/Entry/Exit by default when they are available (It is the case when they are created)

Finally, the action which displays the do/entry/exit when it is set should be managed with an Advice. It is currently managed with a listener, and does not work when the diagram is closed.