--
*From:* chris ze.m...@gmx.net
*To:* Nuke user discussion nuke-users@support.thefoundry.co.uk
*Sent:* Monday, 13 February 2012, 11:18
*Subject:* Re: [Nuke-users] node lock?
this is a wild shot, but maybe it's possible replace the
standard delete action with your
To: Nuke user discussion
Subject: Re: [Nuke-users] node lock?
Thanks for the ideas, guys. seems like it might be possible.
I'm trying to stay away from any custom delete function, since that's a bit too
high level of a change. the bookmarker script is almost exactly the ticket -
thanks Howard
The only thing that came to mind for me was adding an onDestroy callback
to check whether the node is one we're not supposed to delete:
def showError():
nuke.message(You deleted the wrong node!)
nuke.addOnDestroy(showError, nodeClass='Dot')
I tried triggering an undo during the callback,
this is a wild shot, but maybe it's possible replace the
standard delete action with your own function? (or at least have
the delete keyboard shortcut to call your function)?
that way you could do something like:
if selectedNode is part of a doNotDeleteList
put up alert (or do nothing)
() != 'lock.png'
call built-in delete function
Howard
From: chris ze.m...@gmx.net
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
Sent: Monday, 13 February 2012, 11:18
Subject: Re: [Nuke-users] node lock?
this is a wild shot, but maybe it's
is there any way to essentially lock a node so it can't accidentally be
deleted?
I'm making a template and for organizational sake, some of the expressions
rely on certain dots and noop nodes being in place. without them, my
script looks like a rats nest, but with them it's gold. but I don't
