How Loops Work...

[Dines]

Just a little question about loops.

We see this in the editor, right?

On Loop "Blah"
...

On Loop "Something Else"
...


...and so on. Is the 'On Loop "..."' just ONE condition? Basically, is this statement correct:

- 'Run Loop "My Loop"' executes EVERY 'On Loop' trigger in the frame.
- MMF then tests the parameter of each one, saying "Are you called 'My Loop'?"
- Those who say 'Yes I am "My Loop"' return TRUE, and are executed.


This would mean that if you have 1,000 "On Loop" conditions, but only one of them is named 'My Loop', the action 'Run "My Loop"' would trigger all 1,000. But 999 of them would return FALSE and therefore not run.

[neat_Kliker2]

from what I'm aware, they would all run

[Brandon]

from what I'm aware, they would all run

No, why would loops with different names all run with an on loop action. Dines means that they would all be triggered, but their actions would not be executed because they would return false because of the name difference.

[Sieg]

I think only Clickteam can answer this.

[neat_Kliker2]

oh different names, sorry thought you meant 1000 different condition loops with the same name, they would all run if you ran the loop once

[SEELE]

I don't think that's what he means.

are you asking if having many "DIFFERENT!" fast loops in the same frame would slowdown the execution of any one loop?...

if so then yes however the fact that they do return false means that no sub-conditions within that on loop will be tested and no actions will be taken so it is just string comparing.

(i could be way off what you mean.)

[Olivier]

Clickteam has talked. Look at the last post:
http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Board=2&Number=59209

EDIT: I try to summarize what Yves said some time ago in the french forum:
http://www.clickteam.com/epicentre/ubbthreads.php?ubb=showflat&Number=4843&#Post4843

When you launch a loop, MMF compares the name of the called loop with the name of all the loops created in the frame. MMF will only execute the actions corresponding to the right name, but time was lost due to the name comparison.
The more 'On Loop' events you have, the more time MMF will need to launch them. That's why it's better to store 'On Loop' events in groups and activate these groups only when necessary.

At that time Yves said that it would be nice if some optimization about loops could be implemented at the same time than the HWA version is developed. No news so far.