[r103] New spawned OBJ is triggered by Mouse Click

just want to notify Ashley at this minor but weird thing with Mouse/Touch Trigger, not sure if this change is intentional / by design.

Event Sheet:

<img src="http://i47.tinypic.com/n2e5ub.jpg" border="0">

When comparing how Mouse Trigger works in r102 vs r103

On r102:

• When you click ONCE on the Blue square it will spawn RED circle and text doesn't change ("Circle is NOT clicked")

capx (open it with r102):

https://dl.dropbox.com/u/39382262/BUG/102_MouseClick.capx

html test:

https://dl.dropbox.com/u/39382262/BUG/102/index.html

On r103:

• When you click ONCE on the Blue square it will spawn RED circle and text will change to "Circle is CLICKED"

capx (open it with r103):

https://dl.dropbox.com/u/39382262/BUG/103_MouseClick.capx

html test:

https://dl.dropbox.com/u/39382262/BUG/103/index.html

EXPECTED RESULT:

Not sure, which one is better, both kinda make sense in their own way,

as long as it stay that way (and won't change in the future) I guess it's fine whichever Ashley prefer.

[edit]

Actually when i'm thinking about it, the way r102 works is making more sense,

because when you click on the blue square, Red Circle is not created yet, so Mouse/Touch Click shouldn't trigger Red Circle yet ??

I think that r102 makes more sense. If the conditions would be: is mb1 down, is touching circle, but when its just clicked it shouldn't recognize that circle until the second time when it actually exists before clicking.

It's different in r103 because a bug fix of this issue:

http://www.scirra.com/forum/top-level-event-bug_topic56490.html?KW=

As it is now I think it's a very logical behavior as events are evaluated from the top down.

If you don't want the circle to be clicked you can change the order of the events.

It's not clear which way it should happen, and it depends on engine internals, so I think this has to be closed won't fix. Try not to depend on this kind of behavior.