Basic Question "if Selected"

patbb · October 19, 2005, 9:47pm

Hi!

This is the first script i ever wrote, so sorry for bugging you with basic stuff.

so here is my question:
How do i make a button change if something is selected... just watch the example below:

I have one button,

================================

string $button1 = button -command ("whatever") -label "whatbutton" -bgc 1.0.0;
global proc whatever()
{
int $mods = getModifiers;
if
(($mods / 1) % 2)
select -add sphere1 ;
else
select -r sphere1 ;
}

================================

So this works fine, but now how do i add something like this to the button?:
/////////////////////////////

If sphere1 is selected
button -edit -bgc 0.0.1 = $button1
else -bgc 1.0.0 = $button1

/////////////////////////////

So i want the button to be blue if the object is selected, and green if the object is not selected.

Not only that i would like to had this to my script, but i would like to understand how such a command would be written. mostly out of curiosity.

Thanks!

joojaa · October 20, 2005, 5:33am

does it need to be stativc or is there a need to change the button color on the fly if you ever happen to go and select the object?

amitkhanna · October 20, 2005, 7:40am

Hi there,

Well if you need the color of button changing automatically when you select a sphere or anything for that matter then you will have to use "scriptJobs" ...
If you're new to mel scripting then you might find it a little difficult to set this up but anyways here is an eg:

$scrJob1 = scriptJob -e "RecentCommandChanged" "colorChange";
$scrJob2 = scriptJob -e "SelectionChanged" "colorChange";
$scrJob3 = scriptJob -uiDeleted ropeWindow ("killScrJobProcedure " + $scrJob1 + " " +$scrJob2);

here RecentCommandChanged tracks command changing in maya and
SelectionChanged tracks selecting and deSelecting.

"colorChange" is the procedure to update i.e. change of the button color

So using this you can have your procedure("colorChange") setup to change color of the button.

proc buttonColorUpdate()
{
button -edit -bgc 0 0 1 button1;
}

after you have initialised the scriptJob's its really important to kill them else they keep eating system resources. So you will have to have a kill scripts procedure.

eg:

global proc killScrJob(int $scrJob1, int $scrJob2)
{
scriptJob -k $scrJob1;
scriptJob -k $scrJob2;
}

Hope this helps you
Cheers....

amit.

amitkhanna · October 20, 2005, 7:42am

here's the sample code

I hope this solves your purpose

proc colorChange()
{
string $selObj[] = ls -sl;

if($selObj[0] != "nurbsSphere1")
{
	button -e -bgc 1 4 11 -l "   do Something" -w 100 -align "left" "myButton01";
}
else
{
	button -e -bgc 3 44 8 -l "   do Something " -w 100 -align "left" "myButton01";

}

}

proc ccUI()
{
if(window -ex myWindow01)
deleteUI myWindow01;

window 
	-title "some Window" 
	-wh 100 100
	myWindow01;
showWindow myWindow01;

int $scrJob1 ;
int $scrJob2 ;
int $scrJob3 ;

// Initialise Script Jobs
$scrJob1 = `scriptJob -e "RecentCommandChanged" "colorChange"`;
$scrJob2 = `scriptJob -e "SelectionChanged"     "colorChange"`;
$scrJob3 = `scriptJob -uiDeleted myWindow01 ("killScrJob " + $scrJob1 + " " +$scrJob2)`;	

formLayout myFrmLyt;

button -l "   do Something" -w 100 -align "left" "myButton01";

formLayout -e
	-af "myButton01" "top" 20
	-af "myButton01" "left" 10
	myFrmLyt;

}

proc killScrJob(int $scrJob1, int $scrJob2)
{
scriptJob -k $scrJob1;
scriptJob -k $scrJob2;
}

ccUI;

ewerybody · October 20, 2005, 8:38am

You can parent the scriptjobs to the window, so you don't have to kill them extra and they are killed, when you kill the window.

CODE
scriptJob -e "SelectionChanged" "colorChange" -parent myWindow01;

and you can define vars as you process the command:CODE
int $scrJob1 = scriptJob -e "SelectionChanged" "colorChange" -parent myWindow01;

but when you parent.. of course you don't need the numbers at all.

patbb · October 20, 2005, 1:43pm

wow!

this is more complex then i tought.

I'll need a few hours tonight to make sence of all the codes...

Just wanted to say thank for the replys, i expected only short answers pointing me to basic principles...

thanks again!!

-p

ewerybody · October 20, 2005, 3:31pm

hehe.. my reply was more for amitkhanna than for you. I just read what youwanted to do:

But your definition isn't final: I try to sketch the situation:

You got a scripted window with a button in it, right?
Now you select a sphere and the button shall turn blue just as you selected it?

Or is there something else you do to do the check? Of course you can make another button and a procedure that checks if there is a special object in your selection: e.g.:

CODE
global proc checkMySelection ()
{
//ls :very usefull list-command// -sl is for selection// "[]" because ls returns an array
string $sel[] = ls -sl;
string $itemToCheck = "pSphere1";
int $itemIsInSel; //if you set an int its 0 by default
for ($item in $sel)
{
if ($item == $itemToCheck)
$itemIsInSel = 1;
}
if ($itemIsInSel)
print "Item IS in your selection!\n"; // or turn your button color
else
print "Item is NOT in your selection!\n"; // or turn your button color
}

But if you want it like described first: To change the color of the button as you pick it your object of desire thats an event that has nothing to do with you window at all. You have to create the window with a scriptJob parented to it, so this job acts if the window is open and is killed if you close the window.

Its really not a big deal. You gonna dig it!! CODE
{
if (window -ex myWindow) deleteUI myWindow;
window myWindow;
columnLayout;
button -bgc 1 1 1 myButton;

scriptJob
-parent myWindow
-event SelectionChanged "checkMySelection";

showWindow myWindow;
}

global proc checkMySelection ()
{
//ls :very usefull list-command// -sl is for selection// "[]" because ls returns an array
string $sel[] = ls -sl;
string $itemToCheck = "pSphere1";
int $itemIsInSel; //if you set an int its 0 by default
for ($item in $sel)
{
if ($item == $itemToCheck)
{
$itemIsInSel = 1;
}
}
if ($itemIsInSel)
{ // sometimes the buttons are not updated ot once so make it invisible first
// and visible again
button -e -vis 0 -bgc 0 0 1 myButton;
button -e -vis 1 myButton;
}
else
{
button -e -vis 0 -bgc 0 1 0 myButton;
button -e -vis 1 myButton;
}
}

amitkhanna · October 20, 2005, 3:43pm

Hey ewerybody,

I changesd my script a little as you pointed, So i dont need any extra scriptJob to kill the first two. And its just working fine

I had this extra killing procedure in one of my other script which just wouldnt kill the script jobs on window closure, so i added this extra killing. But anyways its working fine for this example....

But i couldnt understand what you are trying to explain in your last rep.. thoughi understand what the code you wroe does.

Thanks

Amit.

ewerybody · October 20, 2005, 3:53pm

I only wanted to ask if he really needs a scriptJob...

Yea its cool to parent that jobs. Saves a lot of stuff.

amitkhanna · October 20, 2005, 3:59pm

Yeah he mentioned he is new to mel,

It might be possible he finds it difficult at first to understand scriptJobs...anyways best of luck patbb

"hey any idea on how to implement progressBar ???" iam really stuck at it

i want to monitor progress of file being exported... i have asked in my other post but hant got any reply yet...

Thanks,
Amit

patbb · October 20, 2005, 6:49pm

sweet everybody,

it worked perfectly (after a few failed attempt...

I managed to have a window with 3 buttons, each button as a process to select one of the sphere (i needed to have a process so i can use the "shift" key to -add select if i wanted to.)

And all the buttons work correctly and change color if one or all the spheres are selected.

Thanks alot everyone who answered; it was very interesting!

-p

Here is my code if you are curious:

CODE
{