Difference between revisions of "Tag"

From TouchDesigner Documentation
Jump to: navigation, search
(Created page with "Each operator can have a set of text strings that are its "tags". For example, tags can be used to categorize and gather components of a certain user-defined classification, s...")
 
Line 1: Line 1:
 +
{{Glossary
 +
|Title=Tag
 +
|Short=Each operator can have a set of text strings that are its "tags". You can set them and search for them within TouchDesigner.
 +
|Long=
 +
}}
 
Each operator can have a set of text strings that are its "tags". For example, tags can be used to categorize and gather components of a certain user-defined classification, such as 'color filter' or 'audio effect'.
 
Each operator can have a set of text strings that are its "tags". For example, tags can be used to categorize and gather components of a certain user-defined classification, such as 'color filter' or 'audio effect'.
  

Revision as of 12:23, 7 March 2018


Each operator can have a set of text strings that are its "tags". For example, tags can be used to categorize and gather components of a certain user-defined classification, such as 'color filter' or 'audio effect'.

You can put tags on operators in the UI at the top of the Parameter dialog, and via python using, for example node.tags = ['tag 1', 'tag 2']

You can search for operators with specific tags using OP.findChildren() method and the OP Find DAT.

See OP_Class

Any of the procedural data operators. OPs do all the work in TouchDesigner. They "cook" and output data to other OPs, which ultimately result in new images, data and audio being generated. See Node.