r86 OR Condition executed multiple times ?

Not sure if this is by-design,
but i think this is really confusing that OR Condition is executed multiple times as long as the condition is true/fulfilled.

The Action part should be executed only once (when the whole condition is fulfilled/TRUE),
instead of running the action as many times as the condition is true (like right now)

Here is a simple example:



capx:
http://dl.dropbox.com/u/39382262/OrSimple.capx

RESULT:
myNumber: 1    Result: 2, 3, 4, 5
myNumber: 2    Result: 3, 4, 5
myNumber: 3    Result: 4, 5
myNumber: 4    Result: 5

EXPECTED RESULT:
myNumber: 1    Result: 2
myNumber: 2    Result: 3
myNumber: 3    Result: 4
myNumber: 4    Result: 5


Turning the action into sub-event doesn't really work either:


capx:
http://dl.dropbox.com/u/39382262/OrSubEvent.capx

The weird thing is, on this case when myNumber is 1, it only executed once:
RESULT:

myNumber: 1    Result: 2
myNumber: 2    Result: 3, 4, 5
myNumber: 3    Result: 4, 5
myNumber: 4    Result: 5

EXPECTED RESULT:
myNumber: 1    Result: 2
myNumber: 2    Result: 3
myNumber: 3    Result: 4
myNumber: 4    Result: 5



Edited by Potato - 15 Apr 2012 at 10:44pm

hmm.. I'm not sure how to use trigger in this case,
if i trigger it like this:



It still doesn't work,
it still executed multiple times

maybe adding the trigger to each condition instance.

trigger sys mynumber = 1
or
trigger sys mynumber = 2

etc...