I may be missing something embarrassingly obvious but I am unable to figure

out why the following javascript object has an issue when two instances are

utilized. Namely, they appear to have a crosstalk even though there is

nothing that connects them. I tried making function calls local (private)

To test this, open two instances, start their metros, and click on message

Observed behavior: when one is active everything is fine. When two are

active, they appear to pollute each other's output data, making one of them

fail to reach their destination xy positions (they are outputted via third

outlet when such point is reached, hence they are easiest to observe). You

can also slow down interpolation speed by bringing down the third parameter

Desired behavior: two patchers should work independently.

What makes this baffling is that "reset" function call is patcher-specific

as well as (obviously) metro-based output, yet third inlet (which is

stepsize var) affects both of them. Should all data entry go via a function

call (i.e. message "setstepsize n" would invoke function setstepsize(val) {

stepsize=val; })? If so, what is the point in having additional inlets?

var inlets=4; //bang/reset, point list, step value, disable during update

//========================================//

        return this.x+","+this.y;

//This function will reset all data used (including coordinates)

        a = arrayfromargs(arguments);

            schedule_update=true;

            coords=new Array(a.length);

                outlet(0,-1);

                outlet(1,-1);

                changed=1.0;

            mycoords.push(new

coord(parseFloat(a[i]),parseFloat(a[i+1])));

        mycoords.push(new coord(mycoords[0].x, mycoords[0].y));

        current = new coord(mycoords[0].x,mycoords[0].y);

        mycoords[numpts].x=parseFloat(coords[i]);

        mycoords[numpts].y=parseFloat(coords[i+1]);

    mycoords[numpts].x=mycoords[0].x;

    mycoords[numpts].y=mycoords[0].y;

    if(getDistance(current,mycoords[pCnt+1])

        if(pCnt+1==mycoords.length) pCnt=1;    

        //current = new coord(mycoords[0].x,mycoords[0].y);

        //initialized=true;    

            //post(changed+"n");

            changed=changed-0.1;

                //post("finally"+"n");

                update_data();

                current.x=mycoords[0].x;

                current.y=mycoords[0].y;

                animating=false;

    if(!initialized){//if we haven't loaded the coordinates, attempt to

    if(!animating){//calculate our new trajectory

        //post("fromto = "+ current.print());

        //post(" " + to.print() +"n");

        xd=checkDirection(current.x,to.x);

        yd=checkDirection(current.y,to.y);

        distance=getDistance(current,to);

        angle=Math.atan2(yDist,xDist);

        txd=stepsize*Math.cos(angle);

        tyd=stepsize*Math.sin(angle);

    //if we are within our stepsize to the target, put us there and move

        //post("reached = " + current.x + " " + current.y + ", count

        if(pCnt+1==mycoords.length) pCnt=0;

        if (schedule_update) update_data();

//finds the distance between two coord objects

    return Math.sqrt(Math.pow(xDist,2)+Math.pow(yDist,2));

I may be missing something embarrassingly obvious but I am unable to figure
out why the following javascript object has an issue when two instances are
utilized. Namely, they appear to have a crosstalk even though there is
nothing that connects them. I tried making function calls local (private)
but that did not help.

To test this, open two instances, start their metros, and click on message
boxes with number list.

Observed behavior: when one is active everything is fine. When two are
active, they appear to pollute each other's output data, making one of them
fail to reach their destination xy positions (they are outputted via third
outlet when such point is reached, hence they are easiest to observe). You
can also slow down interpolation speed by bringing down the third parameter
closer to 0.

What makes this baffling is that "reset" function call is patcher-specific
as well as (obviously) metro-based output, yet third inlet (which is
stepsize var) affects both of them. Should all data entry go via a function
call (i.e. message "setstepsize n" would invoke function setstepsize(val) {
stepsize=val; })? If so, what is the point in having additional inlets?

//movement.js file
//Max settings
var inlets=4; //bang/reset, point list, step value, disable during update
var outlets=4;

var coords="";
var stepsize=0.1;
var initialized=false;
var schedule_update=false;
var suspend=false;
var changed=0;
var warned=false;
var mycoords=[];
var pCnt=0;
var numpts=0;
var current;
var from;
var to;
var animating=false;
//========================================//

coord.local=1;
function coord(a,b){
	this.x=a;
	this.y=b;
	this.print=function(){
		return this.x+","+this.y;
	}
}

//This function will reset all data used (including coordinates)
function reset(){
	initialized=false;
	if (current) delete current;
	current=null;
	if (mycoords)
	{
		for (i=0; i
	}
	mycoords=[];
	schedule_update=false;
	suspend=false;
	numpts=0;
	warned=false;
	coords="";
	pCnt=0;
	to=null;
	from=null;
	animating=false;
	outlet(3,"bang");
}

//Parse coordinates into our array
function list()
{
	if (inlet==1)
	{
		a = arrayfromargs(arguments);
		if(numpts)
		{
			schedule_update=true;
			coords=new Array(a.length);
			for (i=0; i
			if (suspend)
			{
				outlet(0,-1);
				outlet(1,-1);
				changed=1.0;
			}
			return;
		}
		//post("newn");
		for(i=0;i
		{
			mycoords.push(new
coord(parseFloat(a[i]),parseFloat(a[i+1])));
			numpts++;
		}
		mycoords.push(new coord(mycoords[0].x, mycoords[0].y));
		current = new coord(mycoords[0].x,mycoords[0].y);
		initialized=true;
	}
}

update_data.local=1;
function update_data()
{
	//reset();
	initialized=false;
	numpts=0;
	for(i=0;i
	{
		mycoords[numpts].x=parseFloat(coords[i]);
		mycoords[numpts].y=parseFloat(coords[i+1]);
		numpts++
	}
	mycoords[numpts].x=mycoords[0].x;
	mycoords[numpts].y=mycoords[0].y;
	delete coords;
	coords="";
	schedule_update=false;
	if(getDistance(current,mycoords[pCnt+1])
	{
		pCnt++;
		if(pCnt+1==mycoords.length) pCnt=1;	
	}
	initialized=true;
}

function msg_float(val)
{
	if (inlet==2 && val>0 && val
	{
		//initialized=false;
		stepsize=val;
		//animating=false;
		//pCnt=0;
		//current = new coord(mycoords[0].x,mycoords[0].y);
		//initialized=true;	
	}
}

function msg_int(val)
{
	if (inlet==3)
	{
		if (val) suspend=true;
		else suspend=false;
	}
}

	//if we are within our stepsize to the target, put us there and move
to next coordinates
	if(getDistance(current,to)
		current.x=to.x;
		current.y=to.y;
		//post("reached = " + current.x + " " + current.y + ", count
= " + pCnt + "n");
		pCnt++;
		if(pCnt+1==mycoords.length) pCnt=0;
		if (schedule_update) update_data();
		animating=false;
	}
	outlet(0,current.x);
	outlet(1,current.y);
}

//finds the distance between two coord objects
getDistance.local=1;
function getDistance(a,b){
	xDist=b.x-a.x;
	yDist=b.y-a.y;
	xDist=Math.abs(xDist);
	yDist=Math.abs(yDist);
	return Math.sqrt(Math.pow(xDist,2)+Math.pow(yDist,2));
}

checkDirection.local=1;
function checkDirection(a,b){
	if(b-a
}
//end movement.js file

crosstalk-between-two-instances-of-same-javascript-object

Moving this thread to the javascript forum, please send your replies to the javascript list.

crosstalk between two instances of same javascript object