Scripting and hierarchy and naming approaches

[mark_wilkins]

1) By naming with underscores, you can find all the nodes in a given category easily. For example, get all the eye nodes with

string $eye_nodes[] = `ls "*eye*"`;

2) Same thing. Don't tokenize, just do this:

string $level_2[] = `ls "*_level_2_set"`;

3) You can do that, although I'd probably just list the connections and find the sets in the list.


-- Mark

[tymznd]

:eek:
wow, I never even thought of that.... thank you very much for opening my *eyes*.;)

Now for the stupid question.... I see a ton stuff when I do a basic "ls", it seems to span outside of my current file? I assume that these are shared nodes... is that correct? are they determined by the current "project"... and where do these nodes live?

Where do you store arrays of information that you want to be saved with the file? Is there like a generic array node to just hold whatever?

Am I missing help docs that cover all this?

[mark_wilkins]

Where do you store arrays of information that you want to be saved with the file? Is there like a generic array node to just hold whatever?

You have a couple of options.

You can use an option variable (look up the optionVar command) or you can create a node with custom attributes to hold what you want. The latter probably works better in expressions.

I recommend putting custom attributes on existing nodes where it makes sense, but if you really wanted something like a list of stuff saved in your scene you could always make a node of type "unknown" by doing this. Don't do this in an expression; instead have a MEL script that sets it up beforehand and point your scripts at its attributes:

string $node_name = `createNode unknown -name dataNode1`;

Remember that when you create a node you should always check the return value in case Maya assigned you a different name than you'd asked for, which can happen.

As for why ls returns all those items, many of them are hidden from view by default but still exist in your scene. These are generally called "underworld" nodes.

-- Mark

[tymznd]

but if you really wanted something like a list of stuff saved in your scene you could always make a node of type "unknown" by doing this.

Thanks... and so then I can create my own custom attributes.... where do you usually put lists of stuff?

In the Add Attr window there is the "Attribute Type" but the "Per Particle (Array)" is greyed out?? Is this where you would store strings lists? and if so, how do I un-grey it:)

[mark_wilkins]

You should be able to make arrays with the MEL command addAttr -dt <array type>. Look in the addAttr documentation.

Per particle attributes are different and only apply to particle objects, which is why it's grayed out.

-- Mark

[tymznd]

Mark

Thanks for all of your input. :thumbsup: I have spent the last day going through the docs and reading up on the dev stuff and learning a little about the underworld, etc... The optionVar is really cool to know about as well.

Here is where I am stuck:

select -r one ;
addAttr -ln arrayz -dt stringArray;
setAttr one.arrayz -type stringArray 3 "link1" "two" "th_3";
getAttr one.arrayz;
// Error: The data is not a numeric or string value, and cannot be displayed. //
getAttr -type one.arrayz;
// Result: stringArray //
string $xx[] = `getAttr one.arrayz`;
// Error: The data is not a numeric or string value, and cannot be displayed. //
// Result: //
$test = `getAttr one.arrayz`;
// Error: The data is not a numeric or string value, and cannot be displayed. //
// Result: //


How do I getAttr in order to retrieve the array?

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.