It could be that the dependency link is created within the context of your
expression, so it’s only actually valid while your button code is being
evaluated. Can’t say for sure though.
Once theory: when nuke.toNode('Blur4') is evaluated, the reference count of its
Python Node object may be getting incremented, and it could be that the
dependent() function checks the Blur node’s reference count and what holds
references to it to partially complete its dependent list. Might be worth a
support request for a final answer though.
-Nathan
From: andi
Sent: Monday, June 04, 2012 9:50 AM
To: [email protected]
Subject: [Nuke-python] dependent() - anomali behaviour
This is so weird , i got a scene :
Quote:
set cut_paste_input [stack 0]
version 6.3 v4
push $cut_paste_input
Transform {
center {960 540}
name Transform3
selected true
xpos -500
ypos 103
addUserKnob {20 User}
addUserKnob {22 dep T "node =
nuke.toNode(nuke.thisNode().knob('tonode').value())\nprint node.dependent()"
+STARTLINE}
addUserKnob {1 tonode}
tonode Blur4
}
Blur {
inputs 0
name Blur4
label "value= \[value size]"
selected true
xpos -413
ypos 92
}
in the transform3 node, in user tab, there's a 'dep' button, this button will
print out the dependent() of the Blur4 Node. Surprisingly, the output is
'Transform3' , what is wrong ?
Does anyone have any idea ? a serious bug ? or something i miss ?
Thanx,
Andi
--------------------------------------------------------------------------------
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
