I once saw a comment internally that said from memory: "nuke.scriptClear()
leaves python in a broken state, do not use" as the reason for overriding it. I
will take a look tomorrow and see if there is more detail.
./sam
On Monday, 28 May 2012 at 5:15 AM, chris wrote:
> well, no matter how often i do this here (and in which way) i
> dont get a crash...
>
> maybe check your menu.py and init.py for any nuke.knobDefaults
> or similar on Log2Lin, since my understanding is that the
> difference between the to methods is that the
> nuke.createNode("Node") looks at those values (as does the
> toolbar creation) while nuke.nodes.Node() does not.
>
> otherwise it sounds like a bug, so you might want report this to
> support along with your system specs.
>
>
>
>
>
> On 5/27/12 at 9:05 PM, [email protected]
> (mailto:[email protected]) (Zach
> Lewis) wrote:
>
> > Weird. That didn't crash Nuke, but this did:
> >
> > n = nuke.createNode("Log2Lin")
> > nuke.scriptClear()
> > print "still there?"
> > n = nuke.createNode("Log2Lin")
> >
> > however, the nuke.nodes.Log2Lin() method seems safe... I really
> > appreciate that.
> >
> > Mixing and matching the above two methods, however, seems to
> > crash nuke on nuke.scriptClear()... including adding a regular
> > Log2Lin node from the tab menu. However, it turns out, if you
> > just add a Log2Lin node from the tab menu and go to script
> > clear, that crashes Nuke also. Super weird.
>
>
>
> _______________________________________________
> 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
