Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus/Neon Work Description/Improvements/StateMachineEnhancements"

Line 21: Line 21:
 
* Show sub state-machines (and contents of composite states) in separate, linked diagrams
 
* Show sub state-machines (and contents of composite states) in separate, linked diagrams
 
* Pre-select container in property dialogs for sub-machine, do-activity and so on: Although an element, e.g. a state is already selected, the dialog requires to "find" this element again in the whole model (this is a general issue for many properties, not only in the context of state-machines).
 
* Pre-select container in property dialogs for sub-machine, do-activity and so on: Although an element, e.g. a state is already selected, the dialog requires to "find" this element again in the whole model (this is a general issue for many properties, not only in the context of state-machines).
 +
* When creating a new state machine, an initial state, transition, and state should be created by default.

Revision as of 06:35, 18 May 2016

State-machine enhancements, tracked in Bug 490259

  • Transition editor ("F2" on transition)
    • Input window is very small (it depends on size of existing label, i.e. it is very small initially), see bug 493510
    • The Xtext editor makes incomplete propositions (e.g. CallEvents for operations are only proposed, if a prefix of the operation name is typed)
    • The Xtext editor makes wrong propositions (e.g. additional "/" although it has already been provided)
    • Xtext transition editor only supports natural language, bug 361361
  • A Sub-state is placed in the upper-left corner of a composite state, when it is the first sub-vertex (that is causing transition of a state to a composite state), see bug 493334
  • Do not show the state compartment by default (minor) => state name would be vertically centered.
  • Do not show labels for pseudo states by default (minor)
  • Add accelerators for creation of transitions (already existing for states, but not working. Not existing for pseudo states yet), see bug 493339
  • LinkLF should work also for the state machine editor => may need regeneration.
  • Simplification of the "General" tab of the property view, see bug 493803:
    • Remove properties isLeaf and visibility for all model elements related to the state machine
    • Reorder following properties: trigger, guard and effect to comply with "standard" order (currently, the order is inversed)
  • Additional filtering in selection boxes, e.g. assure that only call events for operations that belong to the class owning the state machine can be selected, see bug 493872.
  • Drag & drop of elements to transition:
    • Drop of reception or signal => create appropriate trigger
    • Drop of operation => create appropriate call event or effect (call of passed operation). Popup for choosing between the two
  • Show sub state-machines (and contents of composite states) in separate, linked diagrams
  • Pre-select container in property dialogs for sub-machine, do-activity and so on: Although an element, e.g. a state is already selected, the dialog requires to "find" this element again in the whole model (this is a general issue for many properties, not only in the context of state-machines).
  • When creating a new state machine, an initial state, transition, and state should be created by default.

Back to the top