hi Francois, We have run into something very similar to this restriction and have asked for a feature to be able to access a nodes internal plugin. The feature has been logged as Bug 31471 and i'd recommend filing another feature request for it so that hopefully it's priority will be increased.
cheers, Josh On Tue, Oct 9, 2012 at 2:32 PM, <[email protected]> wrote: > Hi all, > I am having problems executing an internal node's button. > My plugin (plugin1) creates an internal node (plugin2) and exposes its > knobs as follows: > > void Plugin1::knobs( Knob_Callback f ) { > plugin2->knobs(f); > } > > int Plugin1::knob_changed(Knob* k) { > plugin2->knob_changed(k); > } > > My problem is that plugin2 is also an executable as it implements a > PyScript_knob that uses "currentNode = nuke.toNode(\"this\") \n" > in its script. > However, when running nuke and clicking on the button exposed in my > instance of Plugin1, "this" actually refers to "plugin1" instead of > "plugin2" and nuke tries to execute plugin1 instead of plugin2. > > I have tried to change "this" to this->node_name(), which now returns > "plugin2 in plugin1" but python doesn't seem to understand this as a > name. I guess this could be related to John's earlier question about > internal node names. > > Any thoughts? > Cheers, > > Francois. > > -- > Dr. Francois Pitie, Research Fellow > Electronic & Electrical Eng. Dept. > Trinity College Dublin > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
