Bug R244: OR causes inconsistent selection

[Random]

When using OR, objects do not get selected in a consistent way.

+ mouse over Object A
OR
+ mouse over Object B
=> destroy Object A
=> destroy Object B

would lead to this:
If you point at Object A, only Object A gets destroyed.
If you point at Object B, both objects get destroyed.

With more than one OR (like a OR b OR c) always the object from the last condition is not included with the rest. See example file in the attachment.

EDIT:
What you would expect instead is that either all objects from all conditions are selected or only the conditions from the OR part that was fired make the selection.

[Random]

Ah. If you make more "interesting" constructions with OR, you can uncover even more wacky behavior. Try the one from this attachment.

[Random]

A temporary solution is to add another OR and after that a condition of another object (that is not affected by the event) which you know is never true (like "Alterable Value Z = 123").
Then that object will be the one that is strangely not affected when the other conditions are true and your code is consistent again.

[Sphax]

Logically, in the second example, all objects should be inverted when mouse is over two objects simultaneously

EDIT : You are right, it's strange and it's probably a bug. To correct it, like you said, add :
OR
- Always
+ Never

[Random]

Ah nice. That's even better than my solution.

[Francois]

The problem is corrected, and both examples work fine now.
Just one precision :

To correct the problem, I am obliged to evaluate ALL the conditions of the event, even is the preceeding condition is FALSE. This will make the OR events slower than normal events for a large number of conditions. But due to the speed of nowadays machines, I do not think it has any importance...

[Random]

Ah that's a shame. But still better than having it work wrong.

When can we get the fixed version?

[Yves]

I'm building it.

[Sphax]

But is an "OR line" will be at the same speed than a duplicate line (like we do before), slower or maybe faster ?

[Random]

I think it depends. If you have (simplified) conditions like this:

+ fast condition
+ slow condition
=> do something

+ fast condition2
+ slow condition2
=> do something

That will run faster than writing

+ fast condition
+ slow condition
OR
+ fast condition2
+ slow condition2
=> do something

Because with the or, the slow conditions get checked even if the fast condition is not true.