Comment 1 Thomas Jung 2011-03-19 14:34:37 EDT

Additionally it doesn´t matter if there are really two incomming transitions or one transition with two trigger events.
Both constallations do not work. That´s not good.

This error leads to a null pointer exception of the generator.

Comment 2 Thomas Jung 2011-03-19 14:48:53 EDT

Two possible triggers might be caused by a update problem

Comment 3 Henrik Rentz-Reichert 2011-06-01 06:44:48 EDT

Decision of discussion with ts and tj:

- for performance reasons and to simplify handling a Message can have only 0 or 1 data arguments
- message data are available (and passed to the action code methods) until the transition chain hits the first transition point
- cp branch transitions must not connect to their source cp
- entry points and choice points may have more than one incoming connection

Hints for implementation:
to avoid code duplication common chain segments should be identified and factored out

This will not be implemented for the first release.

Comment 4 Henrik Rentz-Reichert 2012-06-27 03:27:33 EDT

This is possible now with commit 29c53d11aa5e9c33423de5df90874f14502cead6.

The check of data compatibility is postponed to bug 383609.
The optimization by identifying common parts of transition chains is postponed to bug 383610.

Comment 5 Henrik Rentz-Reichert 2012-10-12 03:42:54 EDT

Part of eTrice 0.2