Constraints after bad conditions are still triggered

[jcelerier]

As can be seen in this picture.
First condition is 1 == 1, second condition is 1 == 2

bad_condition.scorejson.txt

[theod]

I'm looking at this trouble.
for the record I can't build such kind of scenario myself. when I click on parentEvent and if I edit the condition it appears on the highest event only. but maybe this is not available on master ?

[theod]

hum ... I can't reproduce this trouble on my side (I did a clean and fresh build after updating i-score and API on master)

[theod]

ok I've managed to recreate the scenario myself too : I forgot about the split feature (which not user friendly but this is another topic)

[theod]

this seems to be fixed.
actually I've never encountered such trouble during the whole dev I did recently on execution (testing trigger and condition) so I close the issue