| scope of trigger/message parameters [message #1776580] |
Fri, 17 November 2017 15:40  |
Eclipse User |
|
|
|
Hi,
if a transition with a trigger with parameter goes into a choice point,
it appears that the parameter is only available in
- the effect of the transition going into the choice point, and
- the guards of any transition going out of the choice point,
but *not* in the effect of any of the transitions going out of the
choice point.
This seems odd. Also, looking at the generated code, 'msg' is
passed into the transitionaction (corresponding to the transitions
going out of a choice), meaning that only a 'define' is missing, as in,
e.g.,
> #define c ( *(int *)msg->getParam( 0 ) )
A similar problem occurs in local transitions with triggers with
parameters where the parameter is not available even in the effect
of the transition with the trigger that has the parameter (see second
attached model).
Juergen
|
|
|
|
| Re: scope of trigger/message parameters [message #1776611 is a reply to message #1776583] |
Sat, 18 November 2017 07:35  |
| Eclipse User |
|
|
|
Ok, thanks!
On a related note: should the parameter also be available in the entry code of the target state?
I heard that the scope of the parameter should be the entire transition chain.
I did not check if it can be used in the entry code of the target state.
|
|
|
Powered by
FUDForum. Page generated in 0.03665 seconds
Home