Are you certain it was working properly before? The blending mode is a per element property, and not a node global one. Therefore it should be set on individual elements as desired, and most likely will need a .changed() called on the RotoKnob afterwards.
From: [email protected] [mailto:[email protected]] On Behalf Of Ken Boreham Sent: Thursday, June 09, 2011 9:16 AM To: Nuke Python discussion Subject: [Nuke-python] setting rotopaint properties from callback Hi all. This is something I just came up against and I'm wondering if it's a bug or if I'm just missing something. I can, for example set the blending mode for a rotopaint node with python directly nuke.toNode('RotoPaint1')['blending_mode'].setValue('over') This works fine and updates everything as expected. However using the same (or equivalent) code in a callback does not set it correctly. I tried this with a callback on a NoOp node. Tried calling by executeInMainThread. Tried setting the context to rotopaint node first. Tried same idea from callback directly on rotopaint... None of these worked for me. Any other ideas? Is it a bug? Thanks.
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
