Need help with a piece of Mel Code (again :P )

[fransbaud]

I'm trying to make an expression that works as following:

When a select curveA, curveB.visibility wel set from o to 1 [boulean]
These codes don't work for expressions. The problem with this code
it only works when I've selected curveA and press edit in the Expressions
window.

The code won't trigger by selecting curveA, how do I do that??

My current Mel code:

Mel Code THNX 2 ldunham1

string $select[] = ls -sl;

if($select[0] == "curveA"){

if( curveB.visibility != 0 )
{
 curveB.visibility = 0 ;
}
else
{
 curveB.visibility = 1 ;
}

Mel shorter way THNX 2 Joojaa

string $select[] = ls -sl;

if($select[0] == "curveA"){

setAttr curveB.visibility  (!getAttr curveB.visibility) ;
}

---

[fransbaud]

If anybody can help me with this problem, I would really appriciate it.

THNX

[joojaa]

You should not do this, it violates separation of the gui and xecution environment. What you really want is a new node type instead.

[fransbaud]

He Jooja,

What do you meen with "separation of the gui and xecution environment".

Is the xecution environment like; pressing a button??

My current connections with Curve A and B are as followed:

Group ( Character )
  -Group ( Move )
    -Group ( Scale )
      -Scale_parentConstraint1 (Global_Ctrl)
    -Move_parentConstraint1 (Global_Ctrl)
  -Group ( BaseMesh )
  -Group ( Blends )
  -Global_Ctrl
  -Global_Ctrl_OnOff (Visibility Switch: CurveA)
    -Global_Ctrl_OnOff_parentConstraint1 (Global_Ctrl: CurveB)

Could you give me an example of how I should build up codes for:

When selecting objects, it will check the string Name of the object
and conditions it to a Function like an " if function "

Thnx

[joojaa]

What do you meen with "separation of the gui and xecution environment".

oh yes typo execution environment.

Maya operates on the assumption that calculation is separate thing from the thing that the user is doing. Attributes are part of the calculation core whereas the user interface is pretty free to do whatever it pleases. Now if you do this your going to taint up the execution environment by entagning the gui quite roboustly with the execution environment. They are separated for a reason.

By design nodes are supposed to be totally oblivious about how what or who is accessing them. So setting a node to probe the selection list is a slightly questionable act. You will very fast drop into the gray area of maya programming, and it wont trigger.

You can do this with scripjobs, but you will find its NOT exactly productive in terms of versatility. You would put the data up where it belongs in the gui part of the code. However script jobs get tunred off duirng playback, not a issue in this case but its still a aissue that WILL pop up sooner or later unless you KNOW WHAT YOUR DOING.

But then if you know, theres a much more natural way to do this, and that is to implement your ownlocator node and instead of hiding and making extra nodes in the scene you actualaly draw the thing differently when its selected.