Re: Re: [scxml] bug with script in combination of a chain of transitions
R.C. Hoekstra <r.c.hoekstra <at> erasmusmc.nl>
2015-06-15 20:37:17 GMT
Hi Woonsan, hi others,
At first, sorry for the late reply. I posted the issue in april, but didn't get a response in the first two
weeks. Then I forgot about it (busy with other issues), and then just saw your reply, about a week ago.
Anyway, I've been thinking hard about the issue, and I think I now understand what is going on here.
Then again, sorry that my example wasn't so clear, at first. The problem is we're having very complicated
scxml schemes working with several custom classes, and I tried to bring the example back to the basics, but
probably just missed the key thing.
It basically comes to this, I discovered. Consider this scxml:
<transition event="screening" target="cxr" />
<ntd:test id="CXR" />
<transition event="CXR.negative" target="untreated" />
<transition event="CXR.positive" target="somethingelse"/>
<state id="untreated" />
The custom ntd:test tag fires a CXR.negative event.
Now the SCXMLListener reports this for the onentry's and onexit's