Hi Ben,
yeah it's odd isn't it... I just pinged support@ about it - we'll see what
their response will be.
Regarding setting the value via the constructor - that does indeed allow me
to set the value once.
However unfortunately that is not really an option for our scenario as we
have a few of these knobs that get updated under the hood quite often.
I might however try to destroy and then re-create the knobs to get around
the whole issue... But that does feel a bit dodgy and I'm not really super
excited about having to fiddle around with a piece of core pipeline code
that has been in production for a quite few years now without any such
issues - just to get 'Assist' up and running...
We'll see - but anyway: thanks for your time and your thoughts!
Cheers, Martin
--
Martin Chatterjee
[ Freelance Technical Director ]
[ http://www.chatterjee.de ]
[ https://vimeo.com/chatterjee ]
On Tue, Dec 10, 2013 at 11:33 PM, Ben Dickson <[email protected]>wrote:
> Does seem odd you can add the knob, but not set the value.. Probably
> worth asking support@ about it - there might be some specific reason for
> disallowing it, or the Root node might just have been overlooked
>
> As a workaround, could you set the initial value in the knob constructor?
>
> n = nuke.String_Knob("foo", "foo label" "initial value")
> nuke.root().addKnob(n)
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
