The index of a the input on outputnodename to wire into the new node’s input, or -1. The name of a node to wire into the new node’s output, or "" (the empty string). This list will be non-empty if the user presses MMB or RMB on a node input, which lets the user choose a node to wire into that input.įor backwards compatibility, the kwargs dict also has outputnodename and inputindex, which were used previously when only one output node could be specified. See inputs above.Ī list of nodes and input connector indices that should be wired into the output of the new node. The index of a the output on inputnodename to wire into the new node’s input, or -1. The name of a node to wire into the new node’s input, or "" (the empty string). This list will be non-empty if the user presses MMB or RMB on a node output, which lets the user choose a node to wire from that output.įor backwards compatibility, the kwargs dict also has inputnodename and outputindex, which were used previously when only one input node could be specified. (Houdini uses this internally to record a bbox value for the shape tools based on the geometry they create.)Ī list of nodes and output connector indices that should be wired into the inputs of the new node. This value does not come from Houdini but instead is set for a tool by the bbox attribute in a. If this value is in the dictionary, it contains a bounding box you can use to represent an object, for the purpose of placing. This is set when a tool is invoked in way that has no concept of placement or modifier clicks, for example dragging a node from the Tool Palette in the network editor. (This is separate from checking if ⌃ Ctrl/ ⌘ were pressed.) If this is True, the tool should place the node in the network without asking the user for a position. Whether to create the new node in a branch instead of appending to the current display node. Indicates whether the tool should create a new instance of the node (the usual), or re-use an existing node (for example, the Edit SOP and UV Edit SOP nodes are capable of this). Whether the user was holding ⌘ when they clicked the tool (or selected it from the ⇥ Tab menu). Whether the user was holding Alt ( ⌥ Option on Mac) when they clicked the tool (or selected it from the ⇥ Tab menu). Whether the user was holding ⌃ Ctrl when they clicked the tool (or selected it from the ⇥ Tab menu). Whether the user was holding ⇧ Shift when they clicked the tool (or selected it from the ⇥ Tab menu). The name of the pane in which the tool was invoked (see pane above). If the tool was not invoked in a Scene Viewer (or Context Viewer viewing geometry), this will be None. The viewport in which the tool was invoked. See the scene_viewer() utility function below for a function to get a scene viewer no matter what the value of pane is. In this case, if you need a viewer your script will have to find one, for example with hou.ui.paneTabOfType(). If the tool was invoked from the shelf, this is None. You must also handle the case where the user invoked the tool from a Context Viewer (a viewer type that adapts to the current network). If the tool was invoked in a Scene Viewer, this will be hou.SceneViewer. This dictionary contains the following keys: When Houdini calls your script, it adds a dictionary variable named kwargs to the script’s context.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |