Display node name's of Merge-nodes in the node graph view?

[NEO]

You guys have to excuse me for all my questions. But hopefully they are of use for other newbies to. =)

I noticed that when naming a Merge-node the name ain't displayed in the graph-view. It still displays what kind of Merge it is (i.e. "over"). But I really would like to name those beauties so I can add a prefix to them so I easier can keep a track of what's happening, i.e "over_BackWheel ".

Is this possible?

[nathan]

In the parameters window for the node goto the "Node" tab and enter whatever you want in the "label" text box, the name of the merge will still be displayed in the DAG except below it will be the "label" text.

[NEO]

Aaaah! Is there any shortkey for that one so I can enter the label out in the node view? Just like pressing "n" for changing it's name.

[nathan]

Here is something I cooked up for you, you can add a tcl menu entry or whatever you like to run this command.


knob [selected_node].label [get_input "Enter label text"]When you execute the above command with a node selected it will pop open a window with a text field, simply enter whatever text you want label to be and it will set it for the node.

*edit*
The above code will reset the nodes label if you leave the text field empty and press "Ok", here is a better example that sets the pop up windows text to the current label so if you accidentally press "Ok" with out changing anything it wont reset it.


knob [selected_node].label [get_input "Enter label text" [knob [selected_node].label]]

[nathan]

Here I went a step further and did the work for you, place the "set_label.tcl" file located in the zip attached to this post inside your Nuke user directory. Once you have done that open your "menu.tcl" file and add the following line.


menu "&Edit/&Edit label" "+n" set_labelThis will add a menu entry under "Edit" named "Edit label", it will also add a keyboard shortcut for executing the command to "SHIFT+N". Now all you have to do is click on a node in the DAG, press "SHIFT+N" and it will execute the command to pop open the window to set the label.

[NEO]

WOW! You are crazy man! In a very very very good way! :niceone: This makes me wanna learn nuke even more then I already want! And get more in depth knowledge. Thanks a million nrgy!

May I ask a personal work related question? =) How do you label and name your nodes once you're in a project. Do you never rename them and instead set the label? Or do you add label to the ones (like merge) that does not display the nodes name and rename the others?
Isn't it a bit weird that all nodes ain't acting the same regarding to this? But I guess this has been fine polished in Digital Domains workflow over the years and that this, the current way it works, is the best.

Thanks again nrgy! :D

[nathan]

Well I can see the reason for not being able to change a merge nodes name, personally I find it easier to tell what a merge node is doing by looking in the DAG instead of having to open its parameter window, besides it takes two seconds to set a label if you really want to display something.

Eh I'm horrible when it comes to naming nodes, sometimes I will name things other times I wont it really just depends on what I'm doing. I actually tend to use sticky notes for areas most of the time, although I do name nodes that will be used by something else in an expression because it just makes it easier in that case.

[rueter]

not wanting to hijack your little tête-à-tête here ;) but thought I'd throw in my 2 cents re node names:

the reason the Merge node doesn't behave quite the same as other nodes is actually a feature: If anode has a knob that is called 'operation' than it's value will be displayed in the DAG instead of the node's name. I personally find this very nice as usually with knobs called 'operation' have quite a different impact on the node's output depending on how that knob is set. So I like seeing that value by default.

As for node names vs. labels: I highly recommend not touching node names and getting into the habit of using the labels instead. At the moment expressions in the script may break when node names are changed (i.e. if Blur1 is linked to Blur2, then Blur2 is renamed, the link will break without a warning).
This is something that urgently needs to be fixed but until it is addressed I'd just not rename nodes and use the label instead.

cheers,
frank

[nathan]

Pretty much the same opinions I have rueter, as for the expression breakage I know exactly what you mean.

Wonder what they will do with python and how that will work, the small discussion on the dev list died a while ago but was interesting to follow.

[NEO]

Thanks guys for shining some light upon this. =) It's always good to hear from the pros what one should avoid and why one should avoid it.

Now nrgy's little fix comes extra in handy. =)))