LittleStain thanks! I'm constantly learning a lot from you and it always amazes me how you can find the best solutions to problems. You have my deepest respect!

You can do something like this:

Sprite1.X<Sprite2.BBoxLeft+Sprite1.Width/2--->Sprite1 Set X to Sprite2.BBoxLeft+Sprite1.Width/2

Just add 3 more conditions for right, top, bottom with appropriate values.

That's some very very beautiful work man!

This is so good to hear man, you definitely deserve it and I hope all goes well!

R0J0hound to the rescue! I would never notice there's such a thing if you didn't mention, so thanks man, not only for this but for your whole contribution to this community!

You can already do that and actually it's one of the best features of the event sheet editor!

Just double click to edit the condition and press back until you get at the "page" where you can select a different object. You will notice that when you press next, all the expressions remain intact.

EDIT: It seems I didn't read your post carefully. You can do the above but only for one condition. Still, it's very useful.

Consider this solved! Although I was already running the latest geforce driver, a reinstall fixed the issue.

I'm not posting this to the bugs section because it probably is a problem on my part.

All of a sudden, when previewing a project in NW.js, it applies a reddish tint effect. Firefox/Edge/Chrome work perfectly. It's only NW.js that does this and only in preview. When I export a NW.js project all is normal. See pic bellow. Top is Firefox, bottom NW.js.

I tried uninstalling/reinstalling both R216 and NW.js v0.12.0.

Has anyone encountered such a thing?

LittleStain

Just for your information (<--is this a valid sentence? Not a native speaker :/), firefox throws some script error, while chrome and NW.js works OK.

BTW you guys stop doing awesome things and make the rest of us look like idiots

Congrats man, wishing you the best!

Kyatric thank you a lot for the tip! I'd never thought of that myself and although it seems simple, it's ultra useful.

R0J0hound thanks man!

However, there are situations in which instances of more than one object type are picked and would be handy to have the whole SOL displayed in a table in the debugger.

For example:

Pick Sprite1 by evaluating Sprite1.X>250

Pick Sprite2 by evaluating Sprite2.X>250

If I'm not wrong, when those 2 conditions are inside the same event, C2 picks some instances of Sprite1 AND some instances of sprite2.