wandersonp Posted November 8, 2014 Share Posted November 8, 2014 Im trying to think how to lock the name of a node to maintain proceduralism or when a node need to keep the name even the user try to rename them without realize. I did a simple python inside node, this work but always raise an exception. Any ideas? Quote Link to comment Share on other sites More sharing options...
kgoossens Posted November 8, 2014 Share Posted November 8, 2014 Can you give an example on how you want to use this? Because there might be other way to achieve your goals. Quote Link to comment Share on other sites More sharing options...
wandersonp Posted November 8, 2014 Author Share Posted November 8, 2014 sure I did a screen shot and a hip file to understand my workflow In my work we use the Qube job manager and the render nodes need to be placed in /out. What I want to do is use the same name in "filecache" node and "geometry" rop node and lock the names, to avoid someone(or even me) try to mess in the network later. protect_rename_on_nodes.hip Quote Link to comment Share on other sites More sharing options...
pezetko Posted November 9, 2014 Share Posted November 9, 2014 I'm not sure if forcing (lock) node names has any culprits, but that python way works. Just wrap the OnNameChanged to "try:... except:.." statement to get rid of the exception popup. pz_locked_name.hipnc Quote Link to comment Share on other sites More sharing options...
wandersonp Posted November 9, 2014 Author Share Posted November 9, 2014 pezetko, this technique is really awesome. Thanks a lot Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.