Trigger conditions bug (and workaround)
I've come across a bug that affects trigger conditions in the new triggers design. In my attached example you can see the button has 2 triggers. One opens Layer 1 if the variable %Num% is 10 or less, the other opens Layer 2 if the variable is greater than 10. As you can see, both layers open, meaning that the second trigger is ignoring it's condition.
This bug occurs when you duplicate a trigger and then edit the conditions such as removing one of them.
The most difficult part is to spot that you have this problem as you may be staring at the simplest triggers and conditions wondering why it isn't working. Fortunately, once you know that you have this problem, the workaround it pretty simple. You can either
a) Delete and remake the trigger from scratch
b) If you drag the conditions to rearrange them (this can be done even if there is only a single condition) then I think that remakes them in the new order which also removes the problem.
But anyway, please fix this Articulate.