OR operator (filtered) Have I missed something?

[Outcast]

I have used "OR operator (logical)" very much in my applications, but I have never looked at the "OR operator (filtered)"

I just recently read up on it in the help file however and it sounded extremely useful

I thought I had understand how it works, but apparently not, because the event I made did not work as expected. I wanted to do groups of identical conditions with 3 different objects with OR (filtered) in between and then a create a new object object at 0,0 of these objects if they collided, and from the description I thought that this OR was suppose to handle them individually and only create the new object at 0,0 of the object that actually got its condition true. I will attach a picture of my event so you can see better what I mean.

If this is not possible then what use do the OR operator (filtered) really have? I thought this was what this event was supposed to do from reading this description?

""
The Filtered OR operator
This is the operator you should use in most of the cases. Imagine the following conditions and actions :

+ Mouse is over object 1
OR (filtered)
+ Mouse is over object 2
- Destroy object 1
- Destroy object 2

If the mouse is over object 1, then object 1 is destroyed, but object 2 remains there. If the mouse is over object 2, object 2 is destroyed but object 1 remains there. The filtered OR operator explores all the conditions of the event, and marks all the objects as inspected. The objects contained in false condition are marked as well, but the action related to them will not occur. This is the reason why actions in a event with the filtered OR operator will only affect the objects selected in the conditions that are true.
""

[Jeff]

The only actions that are filtered out are the actions under the objects.
Actions in any of the system objects or other objects will all be triggered if any of the OR statements are true.

[Outcast]

The only actions that are filtered out are the actions under the objects.
Actions in any of the system objects or other objects will all be triggered if any of the OR statements are true.

Ah yes I got told told this. But why is there no 3:rd OR option?
I could think of hundreds of events in my current app to group together instead of having to make tons of extra events if this was possible.

Here is my suggestion for a 3:rd OR option that would be incredible useful. This 3:rd OR would work as the filtered one, but also ignore all actions that involve the objects that are PART of the condition but not part in making the condition true. For example in my event that I showed here I have 3 conditions separated by an OR statement. The 3 conditions are about a collision involving Yellow Diamond and object A OR a collision involving Red Diamond and object A OR a collision involving Purple Diamond and object A. So if it is the Red Diamond that registers a collision with object A, then all actions should be carried out, except those that in any way involve the objects that are also in the OR condition but not true. Because Yellow and Purple are part in the OR conditions, but these objects did not take part in the actual true condition, the Red and Yellow Diamond should be excluded from any actions that involve them in the event line.

[Jeff]

Maybe something could be looked at for version 3 but I think it can't happen before then sorry.

[Outcast]

Maybe something could be looked at for version 3 but I think it can't happen before then sorry.

Ok sounds good!