What about using Op::setKnobsToContext() before calling Op::force_validate()? This seems like that's what you’re trying to do if you truly own the Op pointer.
-jonathan On Dec 29, 2014, at 5:00 PM, Johannes Saam <[email protected]> wrote: > Interesting! I check that out... > i am still stuck on my case... so i am NOT outside nuke.... I just wanna use > the values of an Iop ( and otheres ) to be accessible in my plugin outside > the beaten path.... > > copy pointer to somwhere > later access the Iop basics > > but i can never ever get the validate to run properly... and no calling > knobs() wont work. > > Damn i just want to validate a node on its own.... is it just not possible to > save pointers?? In _validate i copy the pointer and even validate the node > here.... but my pointer never gets valid...i might just have to copy copy the > values there but then i loose the connection... that would be lame! > > On Mon, Dec 29, 2014 at 4:46 PM, Jonathan Egstad <[email protected]> > wrote: > On second thought, to be honest I don’t think you can realistically call > Op::knobs() from outside Nuke without significant trouble - Op::knobs() needs > to be called twice, first to have the Op create the knob objects then to have > each knob object store. You implement two subclasses of > DD::Image::Knob_Closure - one configured as a knob creator and one as a knob > storer. BUT - this is exceedingly non-trivial and is not intended to be done > by a plugin developer as you’ll need to support all the various knob callback > macros which is just not practical…) > > > _______________________________________________ > 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
