PRIORITY TWO In Update annotation, the condition only works in the generated editor, not in the dynamic
PRIORITY TWO This is essential to do do annotations with the update annotations.
In the generated editor, all works well.
In the dynamic editor, the Condition part of an update annotation is ignored. Like this, it is not possible to write update anntations, that do different things depending on a value (!). For instance it isi impossible to implement do actions with update annotations.
In this example updateConditions_202402070100.mcore I define a class with two counters, and two switches to turn increment on and off. The doIncrement feature then triggers two update annotations, both guarded by an update condition. The first update increments counter 1, if increment1Switch is true, the second increments counter 2, if increment2Switch is true.
As you can see in the screencast, this works only in the generated editor. The dynamic editor ignores the conditions, and always increments both counters. Here is the screencast:
REMARK: this will be a perfect test case for add-update to integer features. You only have one counter, but two increments, that will be switched on and off with the conditions.