Multiple intFields using one function?

[Nyro]

The solution is to define setOddInt to accept a string argument that holds the name of the intField to edit.

Here's pseudocode:


window MyWindow;
rowLayout -nc 3;

// first, just create the intfields (name as result into variables)
$int1 = intField "one";
$int2 = intField "two";
$int3 = intField "three";

// now, with the variables populated with the names, each
// intField's -cc can be supplied with that field's name.
// Hence creating and editing the fields is separated into 2 commands*

intField -e -cc ("setOddInt " + $int1) $int1;
intField -e -cc ("setOddInt " + $int2) $int2;
intField -e -cc ("setOddInt " + $int3) $int3;

showWindow myWindow;

proc setOddInt(string $intfield) {
int $value = intField -q -value $intField;
int $oddInt = $value/2*2+1;
intField -e -value $oddInt $intfield;
}

// * Perhaps Python has a way to do this 'in one go'


I separate the intField's creation and the subsequent assignment of a -cc into 2 commands, because the following will not work (in MEL anyway):

$intField_1 = `intField -label "one" -changeCommand("myFunction " + $intField_1)`;

In MEL, you get a variable unkown error because you can't use $variableName in the declaration of $variableName (self-referencing).
Perhaps Python offers a way to do this more elegantly.

[djx]

Unless you want to switch back to mel, I would suggest using a lambda function.

def exampleWin():
win = mc.window(title = "Help me!")
layout = mc.rowLayout(nc = 4)
fieldOne = mc.intField("one", changeCommand = lambda x:setOddInt("one"))
fieldTwo = mc.intField("two", changeCommand = lambda x:setOddInt("two"))
fieldThree = mc.intField("three", changeCommand = lambda x:setOddInt("three"))

mc.showWindow(win)

def setOddInt(field):
oddInt = mc.intField(field, q=True, v=True)
oddInt = oddInt/2*2+1
mc.intField(field, edit = True, value = oddInt)

exampleWin()

David

[PozestStar]

Many thanks to both of you.

Nyro, I'd seen people create fields and later edit them, but I didn't do it because I thought it took up too much space :banghead: I'm learning that that wasn't a good idea. I think I'm going to go back and take your advice.

djx, your lambda solution worked perfectly.

Thanks again for helping me. I really appreciate it!