The Maya file is empty. And right off the bat the last if then lines are going to throw a syntax error as soon as you comment them in because the statements are inside curly brackets yet are missing semi colons. My suggestion is, until your totally comfortable with MEL, make better use of white space so it's easier to pick up on these mistakes. And adding more comments wouldn't hurt

before

Code:

if ( $trackCheck01 == 1 ) { print "Green \n" }
else { print "Red \n" }

after

Code:

if ( $trackCheck01 == 1 ) { 

print "Green \n"; 

}else { 

print "Red \n";

}

Also, you can create another procedure that you pass the variable(s) to.

like:

Code:

global proc doThisStuff(int $curFrame){


print $curFrame;
//and do other stuff


}

If you need to pass multiple variables then just separete them by commas and remember to define the data type(int, string etc). You can even send a mix of data types.

The RT_Check proc can call it.

Code:

global proc RT_Check ()
{
	// expres. on locator runs every frame this procedure... "RT_Check ()"
	spaceLocator ;
	rename |locator1 "tracker01" ;
	addAttr -ln "expr_Pull_Frame" -at long |tracker01;
	setAttr -e-keyable true |tracker01.expr_Pull_Frame;

	int $curFrame =`currentTime -q` ;
	int $prevFrame = $curFrame - 1 ;
	print ($prevFrame + " Previous \n") ;
	print ($curFrame + " Current \n") ;
	print "\n" ;
	select -r tracker01 ;
	delete ;

	int $trackCheck01 = `getAttr pSphere1.inP01` ;
	print ($trackCheck01 + " Visible Status \n") ;
	print "\n" ;

	if ( $trackCheck01 == 1 ) { 

		print "Green \n"; 

	}else { 

		print "Red \n";

	} 

	//// call new proc and pass variable
	doThisStuff($curFrame);


}

Hopefully that helped. I'll stop rambling now

Originally Posted by Gen

You closed the procedure and the "if then" block just fine, you were just missing the semi colons, that's all. Glad it worked out!

Originally Posted by Gen

You closed the procedure and the "if then" block just fine, you were just missing the semi colons, that's all. Glad it worked out!

Originally Posted by Gen

You don't have to create a new topic since this is all part of the same project. There is a scripting section though. I haven't seen a lot of talk about Kinect on here and I personally don't use it so all I can do is help you with your mel scripts lol.

I'm having a lot of trouble visualizing your problem. Do you have any screen shots and mock ups of what you want this thing to look like and function?

Originally Posted by Gen

I don't quite know what I'm looking at. Are the comments in these current? They seem to be experiments and repeated lines that have been commented out and it's adding to the difficulty reading your code.


Also this:

Code:

spaceLocator ;
rename |locator1 "tracker01" ;
addAttr -ln "expr_Pull_Frame" -at long |tracker01;
setAttr -e-keyable true |tracker01.expr_Pull_Frame;

int $curFrame =`currentTime -q` ;
int $prevFrame = $curFrame - 1 ;
print ($prevFrame + " Previous \n") ;
print ($curFrame + " Current \n") ;

select -r tracker01 ;
delete ;

An object was created, an attribute added to it, nothing further is done with that information then the object was selected and deleted. Now you see why I was asking for clarification on how you want this thing to work.

If you needed to find out the keys set on a given attribute you could use the keyframe command.

Code:

keyframe -query pSphere1.inP01;

In this case, it'll return 1 18.

I also saw some issues in the "switchMoment" proc:

Code:

global proc switchMoment (int $curFrame, int $prevFrame, int $trackCheck01)
{
//.... here i have to define he only gives the one frame the swith goes on,
//.... else he keeps recalculation this rule every frame, and need to fetch just that one frame it switches
if ( $trackCheck01 == 0 )
{
print "Non-Active \n" ;
}
else
{
	//Gen: the code is only concerned if the value of trackCheck01 is non zero, 
        //the next if then statement specifying 
	// what it should do if the value is 1 will overwrite this
	
print ($curFrame + " Start Frame \n") ;
//string %colRed = `textField -rgb 1 0 0` ;
}

if ( $trackCheck01 == 1 )
{
	//Gen: you already told it to do something else if trackCheck01 isn't equal to 0
	//So what do you want, this or the command in the previous if then statement?
	
print "STOP Non-Active \n" ;
}
else
{
	//Gen: Same thing here, this "else" value could be turn out to be 0
	
print ($curFrame + "STOP Start Frame \n") ;
//string %colRed = `textField -rgb 1 0 0` ;
}
}

Also, you may want to consider giving your global variables and procedures more specific names. "menuDisplay" and "switchMoment" will likely run you into trouble later down the line if you start making(or downloading) more scripts. And hard coding object names into the script could prove to be problematic. Having the code depend on "pSphere1" could really limit the script's use.


About the auto updating of the current/previous frame UI elements. Since you've set those int fields to have a global scope, you can just add a couple of lines to the RT_Check proc that edits them whenever the proc runs.

Code:

	intField -e -v $curFrame inP_CF;
	intField -e -v $prevFrame inP_PF;

They could probably use more detailed names too haha. You could take this approach to the on/off controls as well.

example

Code:

//........ What to do whith what state............
if ( $trackCheck01 == 1 )
{ print "Green \n" ;

text -e -bgc 0 1 0 aDetailedControlName;

switchMoment ($curFrame, $prevFrame, $trackCheck01);

//string %colGreen = `textField -rgb 0 1 0` ;
}
else
{ print "Red \n" ;

text -e -bgc 1 0 0 aDetailedControlName;

//string %colRed = `textField -rgb 1 0 0` ;
}

Originally Posted by Gen