2009

Together, the if statement and the evaluation mean that only if the result
of the window existence query is “1” (the window exists) is the window
deleted. Otherwise, the section of code within the curly braces is skipped.
Storing control names
If you refer to a control in your user interface, it must have a name. Instead
of manually specifying the name for each user interface element, you can
allow the command to generate unique default names and then you can store
the name as a variable.
All user interface commands return their full name and path upon creation.
You can store the return value as a variable to refer to the control at a later
point in the script.
To store a control name as a variable
1 Type the following in a MEL tab of the Script Editor:
window -resizeToFitChildren 1 pick_me_window; columnLayout;
$button_one=`button -label "Click Me!" -command "deleteUI
$button_two"`; $button_two=`button -label "NO!, Click Me!!"
-command "deleteUI $button_one"`; $button_close=`button -label
"Close" -command "deleteUI pick_me_window"`; showWindow;
We’re using backticks for evaluation again here, though in this case, we’re
creating three variables ($button_one, $button_two, and $button_close)
that hold the results of calling the button command each time.
2 Press one of the “Click Me!” buttons in the window to test the script.
Clicking one of the “Click Me!” buttons deletes the other button by
calling the deleteUI command with the variable that stores the name of
the button control as an argument (button_one or button_two).
(If you click the button a second time, you’ll get an error as the button
you’re trying to delete has already been deleted.)
3 Close the window by pressing the Close button in the window.
When you created your user interface window, you assigned it a unique
name manually. This is a good practice to ensure that you cannot open
multiple copies of a user interface. With more complicated user interfaces,
Window naming | 629