Arima nemo Potato
i believe i see what arima is talking about now, and i think i agree with him. in a normal programming paradigm;
If right arrow is down
or
If D is down
- set sprite x to sprite.x+1
should only execute once if either condition is true.
nemo, your example is slightly inaccurate to what arima is trying to say. your example expresses 'how much' you would get sick from drinking either glass of dirty water, but arima is simply stating this...
If you drink dirty blue glass water
or
If you drink dirty yellow glass water
how much you drink is not important in this logic condition. only whether you will get sick.
i think arima is saying that the event should only execute once in the event of any or all conditions being true. which is the way it is 'interpreted' in programming logic. if you desire an event to execute with true conditions than you can design the events to do that, but by default...they should not.
am i correctly understanding you now Arima?
after answering you the first time, i read ash's explanation of how or works, and he explains that multiple true conditions will execute multiple event assessments.
substituting and else condition would require double eventing...
If right arrow is down
- set sprite x to sprite.x+1
else
If D is down
- set sprite x to sprite.x+1
which is counter-intuitive to what the purpose of 'or' is for; to enable the user to connect several varied conditions to the firing of one event set, upon the true value of one, or more or even all of the conditions.
i hope this was clearly explained. i don't want to make arima's point worse, by confusing people about his intent.
and i apologize arima, for not reading thoroughly enough before trying to answer your post. like i said, i'm no c2 expert...lol. but i do agree with your assertion...now that i actually understand it.