OR, IF, ELSEIF, ELSE, WHILE, etc

I like the logic behind the codes very much =D

And figuring out some conditions, I think the best way to achieve them is using these conditionals: OR, IF, ELSEIF, ELSE, WHILE.

Browsing today, one of the forum topics (Branch) did a workaround for some of them, but, I would like know if it's something I'm missing or they aren't in the events to be selected and used as well?

If they aren't used in the standard, I believe the best thing is avoid workarounds and keep my logics to make the same things =]

About the OR, that's something I mean is automatic, because if one of the conditions is not meat, the software will go to the next, the problem is when you want test one first and them the next one ^^

Edited by TELLES0808 - 01 Nov 2011 at 4:51pm

Very nice explanation, thanks @Rojo

The solution with your original implementation
Another implementation using less events

quick question, I have a button that toggles visibility of an object, in events:

on touch end
-- object is visible?
++++ make object invisible
-- object is invisible?
++++ make object visible

this of course loops itself through fully, because the object will be hidden by the first subevent and shown by second one. how to avoid this so it kinda breaks after making it invisible?

Kyatric wrote: @ranma: capx ?: is a conditional operator, which allows you to test conditions in expressions.

i know, but how do you use it with visibility and others. thanks for the response, but this does not apply, or at least i don't know how to use this operator with "make visible / invisible". also I need to retain this event structure, as this is a simplified version of my real problem.