Bugzilla – Full Text Bug Listing
| Summary: | [StateMachine Diagram] Papyrus StateMAchine Editor shall display opaque behaviours in entry/do/exit actions of a state | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Erwan Bousse <erwan.bousse> |
| Component: | Core | Assignee: | Ansgar Radermacher <ansgar.radermacher> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | cletavernier |
| Version: | 0.10.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=369305 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 399864 | ||
This seems close to this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=369305 , but it seems I don't have this problem for transitions, whereas he does. It took some time ... Fixed with commit 1a9022cfd5667fba509adef5374ca7ddc36282b9 for 1.1-maintenance and commit fa12de4dde1e9863d373c830e9cadc81ad377df4 for master. The behavior is a certain number of lines are shown for the body of an entry/exit/do action with an opaque behavior. This number of lines is configurable via the preferences and style sheets. Note that the default number of lines that is shown is 0 and that the behavior name is shown in this case instead (as before). |
When adding an OpaqueBehavior to the "entry" field of a state in a StateMachine diagram, the following is displayed ; /entry OpaqueBehavior name_opaque_behavior Which does not show the content of the OpaqueBehavior (e.g. OCL code). On the contrary, when adding an OpaqueBehavior to specify an action of a transtion, the content - the OCL code for instance - is directly shown, which is much more readable. Which gives : trigger / self.doSomething() In my opinion, actions in transitions and in entry/do/exit fields should be displayed the same way, and more precisely the second way (the OCL code directly - much more readable). That would look like : /entry self.doSomething()