I see.
This is actually a long standing bug/feature request which I just
reported again a few weeks ago.
It would be really nice to see python api fully support the UI paradigm.
On 4/06/12 4:07 AM, andi wrote:
Hi Frank, Thanx for the response. Yeah, that's what i do so far, i
have to explicitly tell the function what to do (just like using
'mode' argument). I thought there's a way to tell my function what to
do without having to drive it 'manually' .
Anyway, what i want to do is to create a 'working level' function() so
the 'nuke.selectedNode()' will return the correct result. As we now ,
if we jump inside a group then when from script editor we run
'nuke.selectedNode()' , it won't pick up nodes from that level, it
will by default using 'root' level. So i create a function to invoke
'xx.begin()' command. Where xx is my working level.
if it's called from dag objects (i.e.: node,group,gizmo) then i'll run
: nuke.thisParent().begin()
if it's from panel or menu then no need to call xx.begin(), it will
automaticaly pick up the correct level to work with.
if it's from script editor , xx need to be setup explicitly , e.g.:
nuke.toNode('root.Group1.myGroup').begin()
after calling that function() , the .selectedNode() or
.selectedNodes() will working fine.
Thanx for the info.
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
