[Behavior] moveto

You can check if the obj "Is Moving", after it starts his path, if not he probably reached the destination. Another way is to store the target x/y on a variable/array and later check with the obj x/y to see if they match.

That's a really good idea dEspadas, I didn't thought of that. Thank's !

—

Using "condition:On hit target position", it will be triggered when instance move to target position.

I just saw that a few hours ago ! I'm sorry ...

It's just, I've tried to do that in a sub event and it seems to be impossible.

Thanks for your great work and the reply ! <img src="smileys/smiley4.gif" border="0" align="middle" />

New bug appeared in r103 (until r102 it was ok).

I'm using family with MoveTo. Couple of objects are in this family.

When i run this action:

<font face="Courier New, Courier, mono">family - on MoveTo hit target: family - destroy </font>

I got error:

<img src="https://dl.dropbox.com/u/17601731/forum/movetoTest.jpg" border="0">

CAPX:

https://dl.dropbox.com/u/17601731/forum/movetoTest.capx

Tested on IE, Chrome and FF

Is this going to become an official plugin behaviour? I'd love to make proper use of this!

New bug appeared in r103 (until r102 it was ok).

I'm using family with MoveTo. Couple of objects are in this family.

When i run this action:

<font face="Courier New, Courier, mono">family - on MoveTo hit target: family - destroy </font>

I got error:

<img src="https://dl.dropbox.com/u/17601731/forum/movetoTest.jpg" border="0">

CAPX:

https://dl.dropbox.com/u/17601731/forum/movetoTest.capx

Tested on IE, Chrome and FF

http://www.scirra.com/forum/construct-2-v103-crash_topic56710_page2.html

Let's see if this bug fixed by r103.2

I've used this plugin for 1 year properly, made more than 30 projects,

and got 7 apps published on iOS/Android/Blackberry store.

MoveTo is my favorite stable C2 plugin,

I am glad to erect a statue for her one day if I can. <img src="smileys/smiley9.gif" border="0" align="middle">

tecbug

I will check it latter since it does not be solved in r103.2

tecbug

It seems still engine bug.

I change the action "destroy" to "set position", it works fine.

rexrainbow

Add a wait action (wait 0.1 for example), it will solve this bug.

(It is not a good idea I know, sorry.)

I found workaround. No problem :)

Just reporting a bug.

Ashely

tecbug had reported a bug --capx

I trace the code and found that (line 1339)

"type.instances.length" might have some problem after destroyed(remove reference from array I thought).

In this capx, the item count of "type.instance" become 2 (saw at firebug), but "type.instances.length" still to be 3.

So that

inst = type.instances[2]; (line 1341)

inst will be null.

I'm not sure the root cause, just report what I found.

tecbug

This bug had been fix in r104

Fine

Good to know