Bug 512295 - [Tooling] Make it possible to convert a composite state back to a simple state
Summary: [Tooling] Make it possible to convert a composite state back to a simple state
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: 1.0.2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: Document workaround for now
Keywords: Documentation
Depends on:
Blocks:
 
Reported: 2017-02-16 10:12 EST by Peter Cigehn CLA
Modified: 2017-10-17 14:35 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Cigehn CLA 2017-02-16 10:12:11 EST
With the introduction of the filtering of the region, see Bug 494180, it is not longer possible for the user to remove the region (since it does not really exist) to make the state into a simple state again (if the user for some reason want to "undo" the earlier conversion to a composite state).

The proposal is to make the conversion of a composite state available as a menu choice "Convert to simple state" when right-clicking on a composite state. For consistency we should probably also have a "Convert to composite state" menu choice, which performs exactly the same action as when double-clicking on a simple state (as introduced by Bug 493869).

The menu choices should for consistency be available both when right clicking on a simple/composite state in the model explorer as well in a state-machine diagram.

The "Convert to simple state" should in practice perform the opposite of the conversion to a composite state as described in Bug 493869:

* The region and the nested state-machine diagram shall be removed
* All entry/exit points for all incoming/outgoing transitions shall be removed and the transitions shall be reoriented to the simple state itself.
* A check should be made to ensure that composite state is empty. Either the conversion should simply be blocked (to avoid mistakes), or a dialog should popup indicating that the composite state is not empty and ask the user for confirmation that the contents of the composite state also shall be removed.
Comment 1 Ernesto Posse CLA 2017-10-17 14:35:36 EDT
Mass changing all 1.0.1 bugs to target milestone 1.0.2, because Bug 520039 depends on Bug 526168 which depends on Bug 526167 which modifies plugin MANIFEST files and therefore requires a new service version number in accordance to the guidelines at https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment. Hence the solution to these bugs must be merged as a new version (1.0.1) and therefore all old 1.0.1 bugs should become 1.0.2.