stop fast loop

The image below will hopefully make the words clear.

The current frame >=7 triggers the loop
B=1 is likely true in both cases.
I imagined the first condition being true would stop the loop. This is not so.

I have reset the animation frame (in theory once should be enough) to '0' to be sure the trigger condition is false.

What am I missing here?

http://www.buddhamind.info/mmf/stop_loop.gif

Is Alterable Value B an ID number, or something else? You need to select a specific object in the loop with an "Object: Alterable value = LoopIndex("gift-return")" action.

Thanks DavidN

Quote:

---

Object: Alterable value = LoopIndex("gift-return")

---

I am not sure what this means - at least on first reading.

I am coming from a PHP 'break;' line of thought where, when the condition is found to be true, the loop is broken/stopped.

I have since mocked up the situation.
www.buddhamind.info/mmf/AK_fast-loop_test.mfa
with a mouse click trigger.

I am thinking it is not the trigger but having the condition set correctly. Yes?

Actually I might have misinterpreted the problem - I thought you were looping over a collection of objects, and in the example you gave, even doing it with one object causes the problem. It... looks like the events are all right to me, as well - it's possible that "Stop loop" only actually happens once all loop events have run that time round, but I don't remember noticing this before...

I have had another try using LoopIndex and this works fine.

www.buddhamind.info/mmf/AK_fast-loop_test2.mfa
Value reset on first click
click again and the second object is chosen

The limitation is that I have to set the Value to a sequential 0, 1, 2, 3 system. I can do this in the current game (I speculate positively) but it seems a bit limited if this is the only way to exit a loop.

Are there conditions other than LoopIndex that will exit part way through a loop?

As DavidN guessed, it's correct that "Stop Loop" does not stop a loop instantly, it does stop it after all "on loop" actions have been triggered for this loopindex. It's not the logical way for it to work, but it's how it does work. The best solution is to put your "on loop" actions in a group that you close when you stop the loop. That prevents the remaining "on loop" actions to trigger even for the same loopindex.

# not the logical way for it to work
Logic and computers 'should,' but don't always, match.

Quote:

---

The best solution is to put your "on loop" actions in a group

---

Thanks Nifflas. This worked a charm and has so much more flexibility than being tied to LoopIndex.
A++