allow to choose to disposed or make all events of a TimeNode to happened when a first Max bound is reached

[theod]

this is relative to #22

[theod]

this way the MaxBoundEvent will not be optional and it will be possible to make the EndEvent and the MaxBoundEvent happened.

[theod]

I add @bltzr as he is the one who proposed this feature.

[theod]

I've renamed the issue because it is too complexe to put this property on the TimeEvent class.
see the schema I did to illustrate the problem :

[theod]

the API now provides a new attribute to TimeNode to allow to dispose it when a previous timeconstriant reaches its maximal duration.

[cbossut]

This should be a condition tested against variables in the Expression.
When the max bound is reach, first activate the timeNode, then each
TimeEvent test his Expression, with the variables set according to the way
the TimeNode has been launched.

2016-02-11 11:23 GMT+01:00 theod [email protected]:

the API now provide a new attribute to TimeNode to allow to dispose it
when a previous timeconstriant reaches its maximal duration.

—
Reply to this email directly or view it on GitHub
#25 (comment).

Clément Bossut

[theod]

after pushing this commit I've finally understood that was the same than using an expression.
so I will revert this ugly feature ! but I'll add a new one ;-)