We use a little callback similar to this one that fixed the crashing bug:
myNodeClass = 'Read'
def fixPostageStamp():
k = nuke.thisKnob()
n = nuke.thisNode()
if k.name()=='disable':
n['postage_stamp'].setValue(1-k.value())
nuke.addKnobChanged(fixPostageStamp, nodeClass=myNodeClass)
Not a bad thing to do in any version anyway, even if it is fixed in later
versions.
JRAB
On Jun 2, 2011, at 6:43 AM, Jordan Olson wrote:
> Thanks heaps- I'll look into that next time it comes up. Definitely
> sounds familiar, as I never disable nodes in my own comps (prefer to
> disconnect) which could explain why it only happens to other compers
> here!
>
> Cheers,
> Jordan
>
> On Thu, Jun 2, 2011 at 4:19 PM, villain749
> <[email protected]> wrote:
>> I know of a bug in 6.2 where any group node that has a postage stamp, and is
>> disabled will cause a crash. I haven't seen it on read nodes though.
>> Generally I try to avoid postage stamps whenever possible.
>> _______________________________________________
>> 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
