Just something that I've sometimes wondered about in MMF. I think I'm pretty handy with MMF now but sometimes its thinking just confuses me. I'm hoping that Sketchy, Fifth, Pixelthief or one of those guys more experienced with MMF notice this!
In the picture below, I'm creating 5 active objects and setting their properties. It looks logical but it messes up at run time. The last property is applied (only) to the first-created object.
Does anyone have any insight into this? And in a case where fastloops aren't an option, is there a way to create multiple objects and set their properties in one event? I understand that this particular example can be done easily with fastloops. I'm just trying to figure out how MMF thinks.
I just tried this and it messed up. I was so certain it would work though, as it will let you create an object, then set it's position right afterwards, and continue with other actions the same way you have displayed in the pic.
The reason why this happens is because MMF's object selection is reset every time it creates a new object (and the focus is just applied to the new object). If you have 5 separate events that create the object and set the scale, it will work. Or you could run a fastloop 5 times to create them more neatly.
Also, create at object and create at x,y also influences object selection. It seems it's best to always create the object at x,y and then set the x,y to another object's x,y if you need to. But if you create objects through fastloops (1 object + config conditions per event), this last shouldn't be relevant.
EDIT: By the way, if you're going to use fastloops, put them inside a deactivated group. I always name groups like these "LOOP: Description". When you need to run the events, activate the group, run the loop, and deactivate the group. This way you keep MMF's string pool clean, and that way it avoids having to determine what fastloops need to be run (which can be pretty slow if you have a lot of on loop events).
Advertisement
Post Reply
Edited by Alonso Martin