Instead of Fast Loop

I joined another object to the object by using Fast Loop.

However, processing slows because the loop frequency increases, too, when the number of objects increases.

Is there a method of evading slowing of processing?

http://mfa.aquadasoft.com/view/1288607083-FastLoop_test

Use my Position Controller extension, it has features for object attachment.

I don't know usage of your extension.

Could you make example?

Yes, sure. Here is your example modified to compare fastloops (the 1st frame) to the Position Controller (2nd frame). You can set the global value "Number to make" through the application properties to the number of pairs of objects to make (it would be 230 in your original example).

Here is a list of framerates I got for different numbers to make:

Number to Make = 200:
Fastloop: 60 FPS
Pos. Controller: 60 FPS

Number to Make = 300:
Fastloop: 40 FPS
Pos. Controller: 60 FPS

Number to Make = 400:
Fastloop: 23 FPS
Pos. Controller: 60 FPS

Fast Loops and the MMF object selection scope tend to a time complexity of O(N^2) over N objects. The ForEach object, if you learn it, can operate in O(N) time, because it directly references the objects you want to use.

I'd strongly recommend trying to use the ForEach object for operating over a large set of objects

The Position Controller does the same thing, so for the sake of attachments it is better. But yes, for looping through objects in general the ForEach Object is a good way to go.

Thanks!
However, the application crashes when parent or child object is destroyed.

Moreover, can parent and child object tie?(example: when a parent object is clicked, the bullet is launched from the child object.)

Quote:

---

Originally Posted by ASD

However, the application crashes when parent or child object is destroyed.

---

You just found a bug. I'll have to fix that when I release a new version, but for now you can use either "Detach Single Object" or "Detach Children" on a child or parent before destroying them.

Quote:

---

Originally Posted by ASD

Moreover, can parent and child object tie?(example: when a parent object is clicked, the bullet is launched from the child object.)

---

Yes, you can. Try the following code:

Code:

---

-User clicks on "Parent"
-Fixed value of "Child" = AttGetChild( "Position Controller", Fixed("Parent"), 0):
    --Shoot Bullet from "Child"

---

Quote:

---

Originally Posted by Jaffob

You just found a bug. I'll have to fix that when I release a new version, but for now you can use either "Detach Single Object" or "Detach Children" on a child or parent before destroying them.

---

Okay, I'm looking foward to update.

Quote:

---

Originally Posted by Jaffob

Yes, you can. Try the following code:

Code:

---

-User clicks on "Parent"
-Fixed value of "Child" = AttGetChild( "Position Controller", Fixed("Parent"), 0):
    --Shoot Bullet from "Child"

---

---

Very nice! ;)

Can define the position of the child object related for the parent object? (Currently child object position is parent object hotspots)

thanks for the post

I noticed the child object position when the object was attached.

BTW, I want you to develop the SWF version of this excellent extension to reduce the use of a Fast Loop in the SWF application.

The application crashes when some same objects(parent and child) are destroyed at a time.

http://mfa.aquadasoft.com/view/1288778900-position_controller_attach_example

When the several parents object overlapped, they are clicked.

Quote:

---

Originally Posted by ASD

The application crashes when some same objects(parent and child) are destroyed at a time.

http://mfa.aquadasoft.com/view/1288778900-position_controller_attach_example

When the several parents object overlapped, they are clicked.

---

This crash occurs because of some sort of confusion with MMF's object selection, but I can't really trace it down to anything in particular. It can be pretty much solved by adding the "Pick Active at Random" condition to the last event. I say "pretty much" because it prevents the crashing, but causes the deletion of all the objects to go object by object. You could probably come up with a fix for that if it were really a problem (using fastloops or something), although I think it's actually sort of cool. ;)

I just realized that mostly all operations on destroyed objects will crash the application (a problem I should fix for this object and others of mine as well). I've put this problem on the to-do list for the future, as I am currently quite busy and am also working on a new extension. But the to-do list is only three items long, so I'll fix it as soon as I have time.

EDIT: I forgot to tell you, I also added creating a Flash version of the extension to the to-do list.

Quote:

---

Originally Posted by Jaffob

This crash occurs because of some sort of confusion with MMF's object selection, but I can't really trace it down to anything in particular. It can be pretty much solved by adding the "Pick Active at Random" condition to the last event. I say "pretty much" because it prevents the crashing, but causes the deletion of all the objects to go object by object. You could probably come up with a fix for that if it were really a problem (using fastloops or something), although I think it's actually sort of cool. ;)

---

The application crashed though I added the that condition to the last event.
Could you send example?

Thanks for develop the Flash version.

Sorry, I forgot to tell you. The condition must be the 2nd one in the event, after "Alterable Value = 2."

Yes, inserted the condition after "Alterable Value = 2". But, objects doesn't destroy...

What do you mean? They do when I test it. Could you upload the new example with the condition in so I can take a look?

Ah, sorry. I'm confused the condition "Pick Active at Random" and "Pick an object at random", it worked fine.
Thanks!

Even if the object clicked of the create object in the below event line, it is not deleted when the object is created at the same time.

http://mfa.aquadasoft.com/view/1288931679-position_controller_attach_example2