Order of Events for Loops

Thanks for your effort!

That's interesting, thanks. I wouldn't have expected the for each loop to work that way exactly, although it does make sense

(I've never used a for-each loop so I have no experience with them at all)

Thanks for taking the time to share this.

It would seem like the foreach runs 1 event x loops before it moves to the next event, but take a look at the modification I made. The issue is that the object's iteration is not being considered. Personally, I've avoided using foreach because of its lack of support for qualifiers (it's the only extension I've found that doesn't support them, which beats its purpose completely).

Please login to see this attachment.

Alonso: The ForEach extension has supported qualifiers for ages now - you probably just need to update your copy.

Anyway...
I'm not sure why you're having problems with this - it's pretty straightforward.

Line 1 - MMF2 starts the ForEach loop.
MMF2 picks the first object (the order, like everything else in MMF2, is based on the order in which the objects were created, or for objects created at edittime, on their display order).
MMF2 scans through the complete event list from top to bottom, processing every event with a "on ForEach loop" condition, in the order in which they appear in the event list.
Once MMF2 reaches the end of the event list, that is one iteration done.
MMF2 then moves onto the next object and starts again.

It's just the same as with fastloops.

"Immediate" conditions (the ones written in red), are all handled in exactly the same way, and really loops aren't anything special - they're just actions that trigger an immediate condition, that's all.

The main use of the fixed value in ForEach loops, is for creating nested loops.
For example, one way to make each of multiple player objects look towards their nearest enemy, would be by using nested ForEach loops like this:

+ Always
-> Player: Set StoredDist to 99999999

+ Always
-> ForEach: Start ForEach loop "PlayerLoop" for Player

+ On ForEach loop "PlayerLoop" for Player
-> ForEach: Start ForEach loop "EnemyLoop" for Enemy

+ On ForEach loop "EnemyLoop" for Enemy
+ Player: Fixed value = LoopFV( "ForEach", "PlayerLoop")
+ Player: StoredDist > distance from Player to Enemy
-> Player: Set StoredDist to distance from Player to Enemy
-> Player: Look in the direction of Enemy

Similarly, it's possible to nest fastloops inside ForEach loops, and vice versa.

Quote from MuddyMole

Alonso: The ForEach extension has supported qualifiers for ages now - you probably just need to update your copy.

Anyway...
I'm not sure why you're having problems with this - it's pretty straightforward.

Line 1 - MMF2 starts the ForEach loop.
MMF2 picks the first object (the order, like everything else in MMF2, is based on the order in which the objects were created, or for objects created at edittime, on their display order).
MMF2 scans through the complete event list from top to bottom, processing every event with a "on ForEach loop" condition, in the order in which they appear in the event list.
Once MMF2 reaches the end of the event list, that is one iteration done.
MMF2 then moves onto the next object and starts again.

It's just the same as with fastloops.

Hi MuddyMole,

Do you know if the foreach is working with qualifiers in flash?

I can confirm it does and it doesn't. It's a trick one to narrow down using 'ForEach Group' but my results were very inconsistent, I have been meaning to get something together for Ross to take a look at. My final answer on what I have seen/done would be no, best to just iterate through each object as opposed to a qualifying group (for now anyway)