
Present, the names returned will not include any dag paths. Path as is necessary to make the names unique. Names of any dag objects returned will include as much of the dag This flag modifies the '-n/-nodes' flag to indicate that the Returned may have a copy number appended to the end. If this flag is not present, the file name This flag is not present, the resolved name will be returned.įile name returned will not have a copy number (e.g. May contain environment variables and may not exist on disk). Originally specified when the file was loaded into Maya this path Name and directory path will be returned.įile name returned will be unresolved (i.e. This flag modifies the '-f/-filename' flag to indicate that theįile name returned will be the short name (i.e. OnReferenceNode, parent, referenceNode, shortName, showDagPath, showNamespace, successfulEdits, topReference, unresolvedName, withoutCopyNumber Long name (short name) Related file, referenceEdit Flags child, dagPath,ĮditAttrs, editCommand, editNodes, editStrings, failedEdits, filename, isExportEdits, isLoaded, isNodeReferenced, liveEdits, nodes, Techniques to extrapolate the current name of any affected nodes. You can then use various string manipulation Use the '-onReferenceNode'įlag to limit the results to those edits where are stored on a Use the '-topReference' flag to query only those edits which wereĪpplied from the currently open file. Was applied prior to B:C:pSphere1 being instanced.

Would still return a setAttr edit affecting "C:pSphere1" since it However querying the edits which affect C.ma While A.ma is open, "B:C:pSphere1" may now be anĪmibiguous name, replaced by "|B:C:pSphere1" and Open A.ma and, instead of simply parenting pSphere1, you were to Taken when referenced DAG nodes have been parented or instanced.Ĭontinuing with the previous example, let's say that you were to Since there is currently no node namedĬ:pSphere1 (only B:C:pSphere1) care will have to be taken when In the above example, openingĪ.ma and querying all edits which affect C.ma, would return twoĮdits a parent edit affecting "B:C:pSphere1", and a setAttr editĪffecting "C:pSphere1". Which affect a nested reference, the edits will be returned in the It is important to note that when querying edits If you were then to open A.ma and parent the sphere,Īn edit would be stored on BRN which refers to a node named Sphere, an edit would be stored on CRN which refers to a node named

If you were to open B.ma and translate the Reference to B.ma which has a reference to C.ma which contains a Those edits which affect a nested reference may be stored on

When a scene contains multiple levels of file references, Target, see flag descriptions for more information on what effect A valid target is either a reference node, a Use this command to find out information about references and ReferenceQuery is NOT undoable, NOT queryable, and Note: Strings representing object names andĪrguments must be separated by commas.
