Thanks Ben, I'll use that. Looks like evaluate() should be depreciated
in favour of getEvaluatedValue().
OutputContext should also have a method to handle the localised vs.
non-localised state I reckon. I shall log a feature request for that.
One question though:
Is there a reason you use loop over output_context.viewcount(), then
filter out the default view, instead of just looping over nuke.views()?
Cheers,
frank
On 18/12/13 15:59, Ben Dickson wrote:
With the "evaluate" functions, I tend to find passing an OutputContext
the only reliable way to use them.
Can't remember specifically why.. but the "view" arguments are often
broken, or confusing, or both (e.g accessing the camera 'matrix' for
different views is almost impossible without using OutputContext, also
some take the view name as a string, others take view index but silently
accept a string without error..)
Accusations against Nuke's API aside, this works:
https://gist.github.com/dbr/8016555
On 18/12/13 13:16, Frank Rueter wrote:
I guess <knob>.evaluate() solves it:
for v in nuke.views():
print fileKnob.evaluate(view=v)
On 18/12/13 15:26, Frank Rueter wrote:
Hi all,
is there an easy way to get all file paths for a knob when it's split
for multi view/stereo workflow?
I can't find any methods for this and picking apart the output from
knob.toScript() can't possibly be the answer?!
Cheers,
frank
_______________________________________________
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
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
