Thanks, it looks that the '_eventdata' is available as a root context variable(not in the state's S2 local context thought)
On Dec 28, 2007 6:05 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > Please use descriptive email subjects. The convention (since this is a > shared mailing list) is to use [SCXML] as a prefix followed by a > suitable subject. It also helps the archives to have better subjects. > > On 12/28/07, Lupu Slobodu <[EMAIL PROTECTED]> wrote: > > Suppose the event E1 triggered a state machine transition from S1 to S2. > How > > can one make this event (more precisely it's payload) available for the > > actions being executed by the state S2? > > > > If the actions are within S2's <onentry>, you can access the payload > as the special variable '_eventdata'. > If the actions are in other executable content, you'll need to persist > the payload in a <datamodel> (either S2 or ancestors) using suitable > <assign> statements when the payload is accessible (such as, in S2's > <onentry>). > > -Rahul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
